Skip to content

tobihagemann/turbo / claude/skills/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".

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, write git diff <file> to a patch file, back the unrelated changes out of it (delete their + lines and turn their - lines into context lines), and stage it with git apply --cached --recount <patch>
  • 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.

receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall