stage
The stage skill enables precise Git file staging by identifying modified files with `git status`, selectively adding only relevant changes using `git add` with specific file paths or interactive patching, and verifying staged content with `git diff --cached`. Use this when users request to stage changes, stage files, add files to staging, or prepare changes for commit, especially when distinguishing between related and unrelated modifications in a repository.
git clone --depth 1 https://github.com/tobihagemann/turbo /tmp/stage && cp -r /tmp/stage/claude/skills/stage ~/.claude/skills/stageSKILL.md
# 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 use the TaskList tool and proceed to any remaining task.
For each reviewer question on a PR, recall implementation reasoning and compose a raw answer. Use when the user asks to \"answer reviewer questions\", \"draft answers to PR questions\", or \"explain reviewer questions\".
Apply findings by making the suggested code changes. Applies accepted verdicts, escalates ambiguous findings to the user, and offers to note genuine improvements for later. Use when the user asks to \"apply findings\", \"apply fixes\", \"apply suggestions\", \"apply accepted findings\", \"fix the findings\", or \"apply the review results\".
Assess project-wide structural technical debt: complexity hotspots, deprecated API usage, duplication clusters, and architecture rot. Ranks findings by impact and refactor effort into a report at .turbo/technical-debt.md. Use when the user asks to \"assess technical debt\", \"find technical debt\", \"review technical debt\", \"what should we refactor\", \"find refactoring candidates\", \"where is the code rot\", or \"what's our worst code\". Analysis-only — does not modify code.
Project-wide health audit pipeline that fans out to all analysis skills in parallel, evaluates findings, and produces a unified report at .turbo/audit.md. Use when the user asks to \"audit the project\", \"run a full audit\", \"project health check\", \"audit my code\", \"codebase audit\", or \"comprehensive review\".
Shared changelog conventions and formatting rules referenced by $create-changelog and $update-changelog. Not typically invoked directly.
Run a non-interactive Claude Code print-mode call from Codex. Use when the user asks to \"claude print\", \"ask claude\", \"run claude\", \"consult claude\", or when a Codex Turbo skill needs Claude as an independent peer reviewer.
Enforce existence, reuse, mirror, and symmetry principles to keep new code minimal and consistent with surrounding code. Use when writing new code in an existing codebase, adding new features, refactoring, or making any code changes.
Run autonomous task execution using the codex CLI. Use when the user asks to \"codex exec\", \"run codex exec\", \"execute a task with codex\", or \"delegate to codex\".