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
/simplify-all
Run the code and documentation simplification passes together over one scope, launching every review agent concurrently before applying a single round of fixes. Use when the user asks to \"simplify all\", \"simplify everything\", \"simplify code and docs\", \"clean up code and
Install
$ npx -y skills add tobihagemann/turbo --skill simplify-all --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
/simplify-all
Context preview
The summary Claude sees to decide when to auto-load this skill.
Run the code and documentation simplification passes together over one scope, launching every review agent concurrently before applying a single round of fixes. Use when the user asks to \"simplify all\", \"simplify everything\", \"simplify code and docs\", \"clean up code and
SKILL.md
simplify-all.SKILL.mdname: simplify-all
description: "Run the code and documentation simplification passes together over one scope, launching every review agent concurrently before applying a single round of fixes. Use when the user asks to \"simplify all\", \"simplify everything\", \"simplify code and docs\", \"clean up code and docs\", \"run both simplify skills\", or \"simplify code and docs in parallel\"."
Simplify All
Step 1: Run `/simplify-code` and `/simplify-docs` Skills
Run the `/simplify-code` and `/simplify-docs` skills via the Skill tool in one assistant message, passing along any scope that was provided so both passes cover identical files.
Emit the Agent tool calls for every review agent the two skills define in one assistant message. Each Agent call uses `model: "opus"` and no `name`. Wait for every agent to report before continuing. Do not begin the next step on a partial set, and do not relaunch an agent that has not yet reported. State the count explicitly when emitting the calls. Hold every fix for Step 2 in place of each skill's own fix step.
Step 2: Fix Issues
Aggregate the findings and apply one round of fixes, following each skill's own guidance for resolving its findings.
Once this round's fixes have landed, including any resolved at a gate, make one pass over the agents' findings: any whose verdict depended on code the fixes changed, moved, added, or deleted gets decided again against the current tree, keeping resolutions the user already chose.
Then use the TaskList tool and proceed to any remaining task.
Read more
name: simplify-all description: "Run the code and documentation simplification passes together over one scope, launching every review agent concurrently before applying a single round of fixes. Use when the user asks to \"simplify all\", \"simplify everything\", \"simplify code and docs\", \"clean up code and docs\", \"run both simplify skills\", or \"simplify code and docs in parallel\"."
Simplify All
Step 1: Run `/simplify-code` and `/simplify-docs` Skills
Run the `/simplify-code` and `/simplify-docs` skills via the Skill tool in one assistant message, passing along any scope that was provided so both passes cover identical files.
Emit the Agent tool calls for every review agent the two skills define in one assistant message. Each Agent call uses `model: "opus"` and no `name`. Wait for every agent to report before continuing. Do not begin the next step on a partial set, and do not relaunch an agent that has not yet reported. State the count explicitly when emitting the calls. Hold every fix for Step 2 in place of each skill's own fix step.
Step 2: Fix Issues
Aggregate the findings and apply one round of fixes, following each skill's own guidance for resolving its findings.
Once this round's fixes have landed, including any resolved at a gate, make one pass over the agents' findings: any whose verdict depended on code the fixes changed, moved, added, or deleted gets decided again against the current tree, keeping resolutions the user already chose.
Then use the TaskList tool and proceed to any remaining task.
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