Topic: claude-skills
11,948 skills in this topic.
-
refine-spec
Iteratively review and revise a specification document until no new findings survive evaluation. Runs /review-spec, /evaluate-findings, /apply-findings, then re-runs itself until stable. Use when the user asks to "refine the spec", "refine this spec", "iterate on the spec", "tighten the spec", or "improve the spec".
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
-
turboplan
Analyze task complexity and route to a planning mode. Produces a plan file at .turbo/plans/<slug>.md. Use when the user asks to "turboplan", "run turboplan", "plan this task", "turbo plan mode", "plan and implement", or "use turboplan instead of plan mode".
tobihagemann/turbo 261
-
codex-exec
Run autonomous task execution using the codex CLI. Use when the user asks to "codex exec", "run codex exec", "execute a task with codex", or "delegate to codex".
tobihagemann/turbo 261
-
consult-codex
Multi-turn consultation with Codex CLI for second opinions, brainstorming, or collaborative problem-solving. Use when the user asks to "consult codex", "ask codex", "get codex's opinion", "brainstorm with codex", "discuss with codex", or "chat with codex".
tobihagemann/turbo 261
-
self-improve
Extract lessons from the current session and route them to the appropriate knowledge layer (project AGENTS.md, auto memory, existing skills, or new skills). Use when the user asks to "self-improve", "distill this session", "save learnings", "update CLAUDE.md with what we learned", "capture session insights", "remember this for next time", "extract lessons", "update skills from session", or "what did we learn".
tobihagemann/turbo 261
-
implement-plan
Execute an implementation plan file produced by /draft-plan or /turboplan. Runs pre-implementation prep, loads task-specific skills by matching plan content against available skill triggers, executes the plan steps, and runs /finalize. Use when the user asks to "implement plan", "implement the plan", "execute the plan", "run the plan", "implement plans/<slug>.md", "start implementing the plan", or starts a fresh session to implement a previously drafted plan.
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
-
implement-improvements
Plan and implement improvements from the .turbo/improvements.md backlog after validating them against the current codebase. Use when the user asks to "implement improvements", "work on improvements", "address improvements", "process improvement backlog", "tackle improvements", or "implement noted improvements".
tobihagemann/turbo 261
-
update-pr
Update an existing GitHub pull request's title and description to reflect the current state of the branch. Use when the user asks to "update the PR", "update PR description", "update PR title", "refresh PR description", or "sync PR with changes".
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
-
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
-
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
-
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
-
draft-prompt-plan
Decompose a specification file into context-sized shell plans. Each shell captures the wiring invariants (Produces, Consumes, Covers) and high-level Implementation Steps without committing to file paths. Use when the user asks to "draft a prompt plan", "create a prompt plan", "break spec into prompts", "decompose spec into sessions", "plan prompts for spec", "generate prompts from spec", or "make prompts from spec".
tobihagemann/turbo 261
-
interpret-feedback
Interpret third-party feedback by running parallel internal and peer interpretations to surface intent, correctness concerns, and ambiguities. Use when the user asks to "interpret feedback", "interpret comments", "what does this feedback mean", "clarify reviewer intent", "understand this review", or "interpret these suggestions".
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
-
commit-rules
Shared commit message rules and technical constraints referenced by /stage-commit and /commit-staged. Not typically invoked directly.
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
-
find-dead-code
Find dead code using parallel subagent analysis and optional CLI tools, treating code only referenced from tests as dead. Use when the user asks to "find dead code", "find unused code", "find unused exports", "find unreferenced functions", "clean up dead code", or "what code is unused". Analysis-only — does not modify or delete code.
tobihagemann/turbo 261
-
review-correctness
Analyze code for bugs and correctness problems using strict determination criteria. Returns structured findings without applying fixes. Use when the user asks to "review correctness", "scan my code for bugs", "find bugs in my changes", "look for bugs", "check for bugs", or "run a correctness review".
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
-
split-and-ship
Execute an approved split plan by creating separate branches, commits, and PRs for each change group. Use when the user asks to "split and ship", "ship the split plan", "create separate PRs", or "split changes into branches".
tobihagemann/turbo 261
-
code-style
Enforce mirror, reuse, and symmetry principles to keep new code consistent with surrounding code. Use when writing new code in an existing codebase, adding new features, refactoring, or making any code changes.
tobihagemann/turbo 261