tobihagemann/stage
codex/skills/stage/SKILL.md
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".
$ install --global
skillsauthnpx skillsauth add tobihagemann/turbo stageInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jul 22, 2026, 7:16 AM374.9s1 file scanned
SKILL.md
- 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:
git add <file1> <file2> ...
- Do not use
git add -Aorgit 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.
Related Skills
tobihagemann/user-experience
development
VerifiedTrustedCommunity
Apply a UX lens to a user-facing change: whether it serves the user's real goal and whether the path through it holds together, using the Understanding, Bridging, and Flowing contexts. Use when scoping, planning, or assessing any change that affects what a user sees or does. Loaded as a lens during planning and assessment.
377SKILL.mdUpdated Jun 18, 2026
tobihagemann/user-experience
development
VerifiedTrustedCommunity
Apply a UX lens to a user-facing change: whether it serves the user's real goal and whether the path through it holds together, using the Understanding, Bridging, and Flowing contexts. Use when scoping, planning, or assessing any change that affects what a user sees or does. Loaded as a lens during planning and assessment.
377SKILL.mdUpdated Jun 18, 2026
tobihagemann/assess-technical-debt
development
VerifiedTrustedCommunity
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.
377SKILL.mdUpdated Jun 15, 2026
tobihagemann/simplify-docs
development
VerifiedTrustedCommunity
Run a multi-agent review of code comments and markdown documentation for unnecessary content, then fix the issues. Covers what-restating comments, name-mirroring doc comments, status-update prose, and other documentation noise. Use when the user asks to "simplify docs", "simplify documentation", "clean up comments", "clean up docs", "review documentation", "strip unnecessary comments", "reduce doc noise", or "run simplify-docs".
377SKILL.mdUpdated May 15, 2026