by tobihagemann
A composable dev process for Claude Code, packaged as modular skills.
# Add to your Claude Code skills
git clone https://github.com/tobihagemann/turboA composable dev process for Claude Code, packaged as modular skills. Each skill encodes a dev workflow so you can run it instead of prompting from scratch. Battle-tested with the Opus model.
TL;DR — Three steps to ship:
/finalize — Tests, iterative code polishing, commit, and PR. One command.Everything else in Turbo builds on this loop: a planning pipeline that produces better plans than raw plan mode, a project-wide audit for assessing codebase health, debugging tools for when things break, and self-improvement that makes each session teach the next. There are 60+ skills beyond /finalize. Read on for the full picture.
Turbo covers the full dev lifecycle: reviewing code, creating PRs, investigating bugs, self-improving from session learnings, and more.
Five ideas shape the design:
/finalize runs your entire post-implementation QA in one command. /investigate follows a structured root cause analysis cycle. The skill is the prompt.No comments yet. Be the first to share your thoughts!
/review-correctnessThe one thing beyond skills is CLAUDE-ADDITIONS.md, a small set of behavioral rules added to ~/.claude/CLAUDE.md during setup. The most important one is Skill Loading: without it, Claude tends to skip reloading skills it has already seen in a session, which causes it to silently drop steps in nested pipelines like /finalize. The additions are kept in sync by /update-turbo. See docs/skill-loading-reasoning.md for the full rationale.
The other core piece is /self-improve, which makes the whole system compound. After each session, it extracts lessons from the conversation and routes them to the right place: project CLAUDE.md, auto memory, or existing/new skills. Every session teaches Claude something, and future sessions benefit.
This diagram shows how /finalize composes its pipeline and how the key sub-skills compose. It covers the core workflow, not every skill in Turbo. See All Skills for the full list.
Turbo amplifies your existing process. It shines when your project has the right infrastructure in place:
/finalize runs your test suite and reviews test coverage gaps. Without tests, there's no safety net. If your project doesn't have automated tests, /smoke-test can fill the gap by launching your app and verifying changes manually (it's part of the /polish-code loop), but real tests are always better./finalize runs your formatter and linter before code review. If you don't have one, style issues slip through./finalize commits your changes, which triggers any pre-commit hooks you have configured. Claude Code respects hook failures and fixes issues before retrying. If your project uses tools like husky, lint-staged, or pre-commit, Turbo works with them automatically./find-dead-code (standalone skill, not part of /finalize) identifies unused code via parallel analysis, but it's even better when your project already has tools like knip, vulture, or periphery integrated.The target audience is experienced developers who want to move faster without sacrificing quality. That said, beginners are welcome too. Turbo is a great way to learn how a professional dev workflow looks. Just don't blindly trust outputs. Review what Claude produces, understand why it made those choices, and build your own judgment alongside it.
If your plan is vague, your architecture is unclear, and you skip every review finding, Turbo won't save you. Garbage in, garbage out.
Every skill is a self-contained piece. Pipeline skills like /finalize and /audit compose them into workflows, but each piece works independently too.
Want to swap a piece? For example:
/consult-oracle with your own setup (it's macOS-only and has a cookies workaround)/commit-rules or /changelog-rules with your team's conventions. The pipeline adapts./code-style with your team's style guide. The built-in one teaches general principles rather than opinionated rules, so it's a natural swap point.This is also why analysis skills and workflow skills both exist. /review-correctness analyzes code and returns structured findings. /review-code composes /review-test-coverage, /review-correctness, /review-security, /review-quality, /review-api-usage, and /peer-review-code into one aggregated review. Run the analysis skill when you want a single-concern scan. Run the workflow when you want the combined results.
Skills communicate through standard interfaces: git staging area, PR state, and file conventions.
If Turbo has helped you ship faster and you're so inclined, I'd greatly appreciate it if you'd consider sponsoring my open source work.
Turbo requires Claude Code. Works best with Claude Code Max 5x, Max 20x, or Team plan with Premium seats (pipeline workflows are context-heavy). Additional tools are installed during setup.
External services: ChatGPT Plus or higher (for codex review), and ChatGPT Pro or Business (for /consult-oracle, where Pro models are the only ones that reliably solve very hard problems). That said, /peer-review-code and /consult-oracle are designed as swappable puzzle pieces, so if you don't have access, replace them with alternatives that work for you.
Open Claude Code and prompt:
Walk me through the Turbo setup. Read SETUP.md from the tobihagemann/turbo repo and guide me through each step.
Claude will clone the repo, copy the skills, configure your environment, and walk you through each step interactively.
Run /update-turbo in Claude Code to update all skills. It fetches the latest update instructions from GitHub, builds a changelog, handles conflict detection for customized skills, and manages exclusions.
See the manual setup guide for step-by-step instructions.
The recommended way to use Turbo:
/finalize when you're done implementingPlanning is up to you. You can use Turbo's planning pipeline, your own process, or skip planning entirely and jump straight to implementation. Turbo's core focus is making sure the implementation is as clean as possible for the commit.
/finalize runs through these phases automatically: