Skill
answer-reviewer-questi…
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…
@tobihagemannView SkillDevelopment
Skill
/commit-rules
Shared commit message rules and technical constraints referenced by /stage-commit and /commit-staged. Not typically invoked directly.
Install
$ npx -y skills add tobihagemann/turbo --skill commit-rules --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/commit-rules
Context preview
The summary Claude sees to decide when to auto-load this skill.
Shared commit message rules and technical constraints referenced by /stage-commit and /commit-staged. Not typically invoked directly.
SKILL.md
commit-rules.SKILL.mdname: commit-rules description: "Shared commit message rules and technical constraints referenced by /stage-commit and /commit-staged. Not typically invoked directly."
Commit Rules
Commit Message Rules
- Match the style from `git log -n 10 --oneline`
- Concise and descriptive
- Imperative mood, present tense
- Aim for ≤100 characters in the subject
- No commit description—summarize everything in the message
- Don't reference `.turbo/` content (filenames, acceptance criteria, step numbers, headings) in commit messages. `.turbo/` is gitignored, so these references would be opaque to anyone reading without local copies.
Technical Constraints
- Use `git commit -m "message"` directly—do not use heredoc syntax (sandbox blocks temp file creation)
- Never bypass commit signing (`--no-gpg-sign`, `-c commit.gpgsign=false`). If signing fails, use `AskUserQuestion` to let the user resolve it—they may need to approve a key prompt.
Ships withturbo
A composable dev process for agentic coding harnesses, packaged as modular skills. Turbo has sibling editions for Claude Code and Codex. The Claude Code edition is production-tested.
Get the whole plugin
Other skills on turbo.
@tobihagemannView SkillSkill
apply-findings
Apply findings by making the suggested code changes. Applies accepted verdicts, escalates ambiguous findings to the user, and offers to note genuine…
@tobihagemannView SkillSkill
assess-technical-debt
Assess project-wide structural technical debt: complexity hotspots, deprecated API usage, duplication clusters, and architecture rot. Ranks findings by impact…
@tobihagemannView SkillSkill
audit
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…
@tobihagemannView SkillSkill
changelog-rules
Shared changelog conventions and formatting rules referenced by /create-changelog and /update-changelog. Not typically invoked directly.
@tobihagemannView SkillSkill
code-style
Enforce existence, reuse, mirror, and symmetry principles to keep new code minimal and consistent with surrounding code. Use when writing new code in an…
@tobihagemannView Skill