Claude Skill

stage

Stage implementation changes for commit with precise file selection. Use when the user asks to "stage changes", "stage files", "add files to staging", or "prepare changes for commit".

LLM Mart · 0 points · 17 0 0

Virus-scanned Reviewed automatically before listing.

Full trust report

Download tobihagemann-turbo-codex_skills_stage-b903a85.zip · 0 KB

tobihagemann/turbo 403 31 forks MIT Updated 1d ago

Part of tobihagemann/turbo — 147 skills

Install

skills CLI npx skills add https://github.com/tobihagemann/turbo/tree/main/codex/skills/stage

Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install tobihagemann-turbo@llmmart

Git git clone https://github.com/tobihagemann/turbo.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole tobihagemann/turbo collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Stage Changes

Stage implementation changes with precise file selection.

Step 1: Identify Changes

Run git status to see all modified, added, and deleted files.

Step 2: Stage Files

Stage only the files relevant to the current task:

git add <file1> <file2> ...

Do not use git add -A, git add ., or git add -u — all three sweep in unrelated changes
If a file contains both relevant and unrelated changes, use git add -p <file> to stage only the relevant hunks
Never stage files containing secrets (.env, credentials, API keys). Warn if detected.

Step 3: Verify

Run git status and git diff --cached to verify the staging area contains exactly the intended changes.

Then call update_plan to mark this step completed and continue with the next step of the active workflow.

Files (turbo)

SKILL.md 1 KB

---
name: stage
description: "Stage implementation changes for commit with precise file selection. Use when the user asks to \"stage changes\", \"stage files\", \"add files to staging\", or \"prepare changes for commit\"."
---

# Stage Changes

Stage implementation changes with precise file selection.

## Step 1: Identify Changes

Run `git status` to see all modified, added, and deleted files.

## Step 2: Stage Files

Stage only the files relevant to the current task:

```bash
git add <file1> <file2> ...
```

- Do not use `git add -A`, `git add .`, or `git add -u` — all three sweep in unrelated changes
- If a file contains both relevant and unrelated changes, use `git add -p <file>` to stage only the relevant hunks
- Never stage files containing secrets (`.env`, credentials, API keys). Warn if detected.

## Step 3: Verify

Run `git status` and `git diff --cached` to verify the staging area contains exactly the intended changes.

Then call `update_plan` to mark this step completed and continue with the next step of the active workflow.