Topic: claude-skills
11,948 skills in this topic.
-
review-agentic-setup
Detect agentic coding infrastructure in a project: CLAUDE.md, AGENTS.md, installed skills, MCP servers, hooks, and cross-tool compatibility (Claude Code and Codex CLI). Returns structured findings about agentic readiness without applying changes. Use when the user asks to "review agentic setup", "check agentic setup", "agentic readiness", "is this project set up for AI coding", or "review AI coding setup".
tobihagemann/turbo 261
-
create-pr
Create a GitHub pull request with a drafted title and description. Use when the user asks to "create a PR", "create a pull request", "open a PR", or "submit a PR".
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
-
review-security
Analyze code for security vulnerabilities, insecure patterns, and security regressions using strict determination criteria. References the project threat model when available. Returns structured findings without applying fixes. Use when the user asks to "review security", "check for security issues", "find vulnerabilities in my changes", "run a security review", "analyze my code for security", "security audit", or "security scan".
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
-
codex-review
Run AI-powered code review using the codex CLI. Use when the user asks to "codex review", "run codex review", or "review a commit with codex".
tobihagemann/turbo 261
-
pick-next-prompt
Pick the next ready shell from a prompt plan in .turbo/prompt-plans/ and hand it to /turboplan for fill-in. Use when the user asks to "pick next prompt", "next prompt", "continue prompt plan", "what's next", "next implementation step", or "continue with the plan".
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
-
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
-
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
-
investigate
Systematically investigate bugs, test failures, build errors, performance issues, or unexpected behavior by cycling through characterize-isolate-hypothesize-test steps. Use when the user asks to "investigate this bug", "debug this", "figure out why this fails", "find the root cause", "why is this broken", "troubleshoot this", "diagnose the issue", "what's causing this error", "look into this failure", "why is this test failing", or "track down this bug".
tobihagemann/turbo 261
-
stage-commit
Stage files and create a commit in one step with a message matching existing commit style. Use when the user asks to "stage and commit", "add and commit", "commit my changes", or "commit these changes".
tobihagemann/turbo 261
-
review-dependencies
Detect package managers and discover outdated or vulnerable dependencies. Returns structured findings without upgrading. Use when the user asks to "review dependencies", "check for outdated packages", "check dependencies", "scan dependencies", or "dependency 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
-
recall-reasoning
Recall the reasoning behind a past change by locating the Claude Code transcript that produced it. Use when the user asks to "recall reasoning", "find reasoning", "look up reasoning", "recall implementation reasoning", "find the rationale", "why did I do X", "recall from transcripts", or "find the transcript for this commit".
tobihagemann/turbo 261
-
review-tooling
Detect what dev tooling infrastructure a project has and flag gaps across linters, formatters, pre-commit hooks, test runners, and CI/CD pipelines. Returns structured findings without applying changes. Use when the user asks to "review tooling", "check project tooling", "what tooling is missing", "review dev infrastructure", or "tooling audit".
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
-
draft-spec
Guide a collaborative discussion that produces a specification document at .turbo/specs/<slug>.md. Use when the user asks to "draft a spec", "create a spec", "write a spec", "discuss a project plan", "spec out a project", "design a system", "let's plan this project", "help me scope this", "architect a solution", or "let's discuss before building".
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
-
fetch-pr-comments
Fetch and summarize unresolved GitHub PR review comments without making changes. Use when the user asks to "fetch PR comments", "show PR comments", "check PR for unresolved comments", "list review comments", "what comments are on the PR", "show unresolved threads", or "summarize PR feedback".
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
-
create-changelog
Create a CHANGELOG.md following keepachangelog.com conventions with version history backfilled from GitHub releases or git tags. Use when the user asks to "create a changelog", "add a changelog", "initialize changelog", "start a changelog", "set up changelog", "generate changelog", or "backfill changelog".
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
-
commit-staged
Commit already-staged changes with a message matching existing commit style. Use when the user asks to "commit staged changes" or "commit what's staged".
tobihagemann/turbo 261