mcpbeat

Stage

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

249 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
398
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/tobihagemann/turbo --skill stage

The instruction itself

4 sections, as written by the author

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 or git add .
  • 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.

How to use it

Copy the folder

Take tobihagemann/turbo-stage from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.