.fyi
SkillsMCPPluginsSubagents

Browse by category

DevOps & CI/CD SkillsProductivity & Workflow SkillsOther SkillsProduct & Project Management SkillsDocumentation & Knowledge SkillsCode Review & Refactor SkillsBackend & APIs SkillsAgent Meta & Communication SkillsResearch SkillsSecurity SkillsUX UI & Design SkillsTesting & QA SkillsSee all →

Every Claude Code skill, MCP server, plugin and subagent in one directory. Searchable, comparable, and one command from installed. Live stats from GitHub, npm and PyPI.

We're on Product HuntYour agent's app storeCheck it out →
Agent SkillsMCP ServersPluginsSubagentsCoding Agents
CollectionsOfficial publishersGlossaryFAQBlogSearchSavedFeedback
PrivacyTermsllms.txtSitemap

made with ♥ · © 2026 aaaa.fyi

Independent project · real data from public registries

…/tobihagemann/turbo
home/skills/tobihagemann/turbo
tobihagemann avatar

tobihagemann/turbo

59 skills

View on GitHub
$npx skills add tobihagemann/turbo
SkillInstalls
answer-reviewer-questionsFor each reviewer question on a PR, recall implementation reasoning and compose a raw answer.—apply-findingsApply findings by making the suggested code changes. Applies accepted verdicts, escalates ambiguous findings to the user, and offers to note genuine…—assess-technical-debtAssess project-wide structural technical debt: complexity hotspots, deprecated API usage, duplication clusters, and architecture rot.—auditProject-wide health audit pipeline that fans out to all analysis skills in parallel, evaluates findings, and produces a unified report at .turbo/audit.md.—changelog-rulesShared changelog conventions and formatting rules referenced by /create-changelog and /update-changelog. Not typically invoked directly.—code-styleEnforce mirror, reuse, and symmetry principles to keep new code consistent with surrounding code.—codex-execRun 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…—codex-reviewRun 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\".—commit-rulesShared commit message rules and technical constraints referenced by /stage-commit and /commit-staged. Not typically invoked directly.—commit-stagedCommit already-staged changes with a message matching existing commit style. Use when the user asks to \"commit staged changes\" or \"commit what's staged\".—commit-staged-pushCommit 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…—consult-codexMulti-turn consultation with Codex CLI for second opinions, brainstorming, or collaborative problem-solving.—consult-oracleConsult ChatGPT Pro via ChatGPT browser automation for problems that resist standard approaches.—contribute-turboSubmit turbo skill improvements back to the upstream repo. Adapts to repo mode: fork mode creates a PR, source mode pushes directly.—create-changelogCreate a CHANGELOG.md following keepachangelog.com conventions with version history backfilled from GitHub releases or git tags.—create-handoffWrite a handoff file at .turbo/handoff/<YYYY-MM-DD>-<slug>.md capturing current session state — task, status, open decisions, in-flight changes, next step — so…—create-issuecreate-prCreate a GitHub pull request with a drafted title and description.—create-project-skillsScans an existing codebase and generates project-specific skills that capture inferred conventions such as naming, file organization, framework usage, data…—create-skillCreate a new skill or update an existing skill that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.—create-test-planAnalyze what changed and generate a structured test plan at .turbo/test-plan.md covering four escalating levels: basic functionality, complex operations,…—create-threat-modelAnalyze a codebase and produce a structured threat model at .turbo/threat-model.md covering assets, trust boundaries, attack surfaces with existing…—draft-planProduce an implementation plan at .turbo/plans/<slug>.md. Use when the user asks to \"draft a plan\", \"draft the plan\", \"write an implementation plan\",…—draft-shellsDecompose a specification file into shells with YAML frontmatter.—draft-specGuide a collaborative discussion that produces a specification document at .turbo/specs/<slug>.md.—evaluate-findingsCritically assess external feedback (code reviews, AI reviewers, PR comments) and decide which suggestions to apply using adversarial verification.—expand-shellExpand a shell into a full implementation plan. Verifies Consumes against the current codebase, runs a fresh pattern survey, escalates open questions, and…—explain-thisExplain whatever the user is pointing at right now in plain language: a pending question, a piece of code, an error, a command output, or an artifact like a…—exploratory-testExecute multi-level exploratory testing of the app covering basic functionality, complex operations, adversarial testing, and cross-cutting scenarios, plus…—fetch-pr-commentsFetch and summarize review feedback and conversation from a GitHub PR (unresolved review threads, review bodies, and PR conversation comments) without making…—finalizeRun the post-implementation quality assurance workflow including tests, code polishing, review, and commit.—find-dead-codeFind dead code using parallel subagent analysis and optional CLI tools, treating code only referenced from tests as dead.—frontend-designCreate distinctive, production-grade frontend interfaces with high design quality.—github-voiceShared writing style rules for GitHub-facing output (PR comments, PR descriptions, PR titles, issues, design proposals).—implementLoad code-style and task-specific skills, make the change described by the current context, then run /finalize for QA and commit.—implement-improvementsValidate improvements from .turbo/improvements.md, recommend a working set tailored to what's in the backlog, and run one lane: direct fixes, investigation, or…—implement-planExecute an implementation plan file produced by /draft-plan, /turboplan, or /expand-shell.—interpret-feedbackInterpret third-party feedback by running parallel internal and peer interpretations to surface intent, correctness concerns, and ambiguities.—investigateSystematically investigate bugs, test failures, build errors, performance issues, or unexpected behavior by cycling through…—map-codebaseDeep architecture report that fans out parallel inspections across different aspects of the codebase (structure, tech stack, APIs, patterns, data flow,…—migrate-turbo-filesMigrate legacy files in .turbo/ to current formats. Covers plans and shells (layout split, frontmatter normalization, prompt-plan index cleanup) and…—note-improvementCapture an out-of-scope improvement opportunity so it doesn't get lost.—onboardDeveloper onboarding guide that composes architecture mapping, tooling review, and agentic setup review with setup, troubleshooting, and next-steps agents to…—peer-reviewRun 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\",…—pick-next-issueFetch and rank open GitHub issues by community engagement, present the top 3 candidates, and plan implementation for the selected issue.—pick-next-shellPick the next shell whose dependencies are satisfied and carry it through planning: expand, refine, self-improve, halt.—polish-codeStage, format, lint, test, review, smoke test, and re-run itself until stable.—previewStand up the project's live app and hand it to the user to try a change firsthand, then gate on their verdict before continuing.—recall-reasoningRecall the reasoning behind a past change by locating the Claude Code transcript that produced it.—refine-planIteratively review and revise a planning artifact until no new findings survive evaluation. Supports plans, shells, and specs.—reply-to-pr-conversationDraft, confirm, and post a single conversational reply to GitHub PR conversation comments (issue comments).—reply-to-pr-threadsDraft, confirm, and post replies to GitHub PR review threads. Handles per-category reply formatting, re-fetches thread resolution state so auto-resolved…—resolve-findingsChoose an implementation path (direct or plan) for evaluated findings and dispatch it. Direct path applies fixes directly; plan path runs /turboplan.—resolve-pr-commentsEvaluate, fix, answer, and reply to GitHub pull request review comments and conversation comments.—review-agentic-setupDetect agentic coding infrastructure in a project: CLAUDE.md, AGENTS.md, installed skills, MCP servers, hooks, and cross-tool compatibility (Claude Code and…—review-codeReview code for bugs, security vulnerabilities, API misuse, consistency issues, simplicity problems, or test coverage gaps by running internal reviews and a…—review-dependenciesDetect package managers and discover outdated or vulnerable dependencies. Returns structured findings without upgrading.—review-planReview a planning artifact (plan, shells, or spec) by running internal and peer reviews in parallel and returning combined findings.—review-prReview a pull request by fetching PR comments, running a comprehensive code review, evaluating findings, and dispatching to implementation.—