Stage Changes
SkillFiles & storageStage 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\".
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Stage Changes skill
What this skill tells your AI
The instructions your AI receives, as published by tobihagemann/turbo in codex/skills/stage/SKILL.md and read by ahel’s review.
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 ., orgit 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.
Signals
- GitHub stars
- 402
- Forks
- 30
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
stage-tobihagemann- Source
- github.com/tobihagemann/turbo