Agent skills
Skills you can use with AI coding agents, indexed from public GitHub repositories.
-
simplify-code
Run a multi-agent review of changed files for reuse, quality, efficiency, and clarity issues followed by automated fixes. Use when the user asks to "simplify code", "review changed code", "check for code reuse", "review code quality", "review efficiency", "simplify changes", "clean up code", "refactor changes", or "run simplify".
tobihagemann/turbo 261
-
evaluate-findings
Critically assess external feedback (code reviews, AI reviewers, PR comments) and decide which suggestions to apply using adversarial verification. Use when the user asks to "evaluate findings", "assess review comments", "triage review feedback", "evaluate review output", or "filter false positives".
tobihagemann/turbo 261
-
finalize
Run the post-implementation quality assurance workflow including tests, code polishing, review, and commit. Use when the user asks to "finalize implementation", "finalize changes", "wrap up implementation", "finish up", "ready to commit", or "run QA workflow".
tobihagemann/turbo 261
-
review-quality
Analyze code for cross-file quality issues: duplicated logic, architectural inconsistencies, and abstraction opportunities. Returns structured findings without applying fixes. Use when the user asks to "review quality", "check for duplication across files", "find architectural inconsistencies", "cross-file quality review", or "review code quality".
tobihagemann/turbo 261
-
github-voice
Shared writing style rules for GitHub-facing output (PR comments, PR descriptions, PR titles). Differentiates insider vs outsider voice based on author association. Not typically invoked directly — loaded by other skills before composing GitHub text.
tobihagemann/turbo 261
-
peer-review
Run an independent peer review via codex. Use when the user asks to "peer review", "peer review my code", "peer review my plan", "peer review my spec", "peer review my prompt plan", "get a second opinion", or "independent review".
tobihagemann/turbo 261
-
ship
Commit, push, and optionally create or update a PR for the current staged changes. Use when the user asks to "ship", "ship it", "ship changes", "commit push and PR", or "ship this".
tobihagemann/turbo 261
-
draft-plan
Produce an implementation plan at .turbo/plans/<slug>.md. Use when the user asks to "draft a plan", "draft the plan", "write an implementation plan", "plan this change", "create an implementation plan", "fill in the shell", "expand the shell", or needs a first-draft plan file before refinement.
tobihagemann/turbo 261
-
pick-next-issue
Fetch and rank open GitHub issues by community engagement, present the top 3 candidates, and plan implementation for the selected issue. Use when the user asks to "pick next issue", "next issue", "which issue should I work on", "top issues", "most popular issues", "prioritize issues", or "what should I work on next".
tobihagemann/turbo 261
-
create-test-plan
Analyze what changed and generate a structured test plan at .turbo/test-plan.md covering four escalating levels: basic functionality, complex operations, adversarial testing, and cross-cutting scenarios. Use when the user asks to "create a test plan", "plan tests", "what should I test", "generate test scenarios", "test plan for this PR", or "what are the test cases".
tobihagemann/turbo 261
-
contribute-turbo
Submit turbo skill improvements back to the upstream repo. Adapts to repo mode: fork mode creates a PR, source mode pushes directly. Use when the user asks to "contribute to turbo", "submit turbo changes", "PR my skill changes", "contribute back", or "upstream my changes".
tobihagemann/turbo 261
-
consult-oracle
Consult ChatGPT Pro via ChatGPT browser automation for problems that resist standard approaches. Use when stuck on a very hard problem, when standard approaches have failed, when multiple debugging attempts haven't worked, or when the user says "ask the oracle", "consult oracle", "consult chatgpt", "I'm completely stuck", "I've tried everything", or "nothing is working".
tobihagemann/turbo 261
-
review-test-coverage
Analyze code for test coverage gaps, untested functions, and missing edge cases. Returns structured findings without writing tests. Use when the user asks to "review test coverage", "check test coverage", "find untested code", "analyze coverage gaps", or "what needs tests".
tobihagemann/turbo 261
-
review-spec
Review a specification document: launches an internal spec review and `/peer-review` in parallel and returns combined findings. Use when the user asks to "review my spec", "review this spec", "check my spec", "critique my spec", or wants spec feedback before planning.
tobihagemann/turbo 261
-
refine-plan
Iteratively review and revise an implementation plan until no new findings survive evaluation. Runs /review-plan, /evaluate-findings, /apply-findings, then re-runs itself until stable. Use when the user asks to "refine the plan", "refine this plan", "iterate on the plan", "tighten the plan", or "improve the plan".
tobihagemann/turbo 261
-
refine-prompt-plan
Iteratively review and revise a prompt plan until no new findings survive evaluation. Runs /review-prompt-plan, /evaluate-findings, /apply-findings, then re-runs itself until stable. Use when the user asks to "refine the prompt plan", "refine this prompt plan", "iterate on the prompt plan", "tighten the prompt plan", or "improve the prompt plan".
tobihagemann/turbo 261
-
commit-staged-push
Commit already-staged changes and push in one step. Use when the user asks to "commit and push staged changes", "commit and push what's staged", or "commit staged and push".
tobihagemann/turbo 261
-
stage-commit-push
Stage files, create a commit, and push in one step. Use when the user asks to "stage commit and push", "add commit and push", "commit and push", or "commit and push my changes".
tobihagemann/turbo 261
-
review-pr
Review a pull request by fetching PR comments and running a comprehensive code review with evaluation. Use when the user asks to "review PR", "review pull request", "review this PR", "check PR before merging", or "full PR review".
tobihagemann/turbo 261
-
create-skill
Create a new skill or update an existing skill that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations. Use when the user asks to "create a skill", "make a new skill", "build a skill", "scaffold a skill", "write a skill for...", or "new skill that does...".
tobihagemann/turbo 261
-
review-prompt-plan
Review a prompt plan against its source spec: launches an internal prompt plan review and `/peer-review` in parallel and returns combined findings. Use when the user asks to "review my prompt plan", "review my prompts", "check my prompt plan", "critique my prompts", or wants prompt plan feedback before implementation.
tobihagemann/turbo 261
-
note-improvement
Capture an out-of-scope improvement opportunity so it doesn't get lost. Use when the user asks to "note improvement", "save improvement", "track this for later", "remember this improvement", "note this idea", "log improvement", "backlog this", or "park this idea". Also invoke proactively when noticing something improvable during work that falls outside the current task's scope — briefly mention it to the user and offer to note it.
tobihagemann/turbo 261
-
survey-patterns
Survey the codebase for analogous features, reusable utilities, and existing patterns relevant to a proposed change. Returns structured findings without writing code. Use when the user asks to "survey patterns", "find existing patterns", "look for analogous features", "check how similar things are done", "find prior art for this change", or needs pattern context before planning a change.
tobihagemann/turbo 261
-
smoke-test
Launch the app and hands-on verify that it works by interacting with it. Use when the user asks to "smoke test", "test it manually", "verify it works", "try it out", "run a smoke test", "check it in the browser", or "does it actually work". Not for unit/integration tests.
tobihagemann/turbo 261