Topic: claude-skills
11,948 skills in this topic.
-
doc
Generates, validates, and syncs documentation for any repository type. Produces code-maps, checks doc coverage, finds missing docs, and validates existing documentation against code. Triggers: doc, documentation, code-map, doc coverage, validate docs, generate docs, sync docs, update docs, find missing docs.
boshu2/agentops 271
-
scenario
Author and manage holdout scenarios for behavioral validation. Scenarios are stored in .agents/holdout/ where implementing agents cannot see them. Triggers: "$scenario", "holdout", "behavioral scenario", "create scenario", "list scenarios".
boshu2/agentops 271
-
inject
Inject relevant knowledge into session context from .agents/ artifacts. Triggers: "inject knowledge", "recall context", SessionStart hook.
boshu2/agentops 271
-
bug-hunt
Investigate suspected bugs or run proactive code audits. Triggers: "bug", "broken", "doesn't work", "failing", "investigate bug", "debug", "find the bug", "troubleshoot", "audit code", "find bugs in", "code audit", "hunt bugs".
boshu2/agentops 271
-
review
Review incoming PRs, agent-generated changes, or diffs. Structured review with security, correctness, performance, and maintainability checks. Triggers: "review", "review PR", "review changes", "code review", "review this PR", "review agent output", "check this diff".
boshu2/agentops 271
-
bootstrap
One command to full AgentOps product layer. Sets up GOALS.md, PRODUCT.md, README.md, .agents/ structure, and hooks. Progressive -- fills gaps only. Triggers: "bootstrap", "setup agentops", "initialize repo", "full setup".
boshu2/agentops 271
-
post-mortem
Wrap up completed work. Council validates the implementation, then extract and process learnings. Triggers: "post-mortem", "wrap up", "close epic", "what did we learn".
boshu2/agentops 271
-
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
-
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
-
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-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
-
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
-
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
-
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
-
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
-
review-api-usage
Check API, library, and framework usage in code against official documentation and installed skill knowledge. Flags deprecated APIs, incorrect method signatures, wrong parameter types, version-incompatible patterns, and best-practice violations. Use when the user asks to "review API usage", "check API usage", "verify against docs", "check library usage", "validate API calls", "check against documentation", or "check for deprecated APIs".
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
-
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
-
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
-
update-dependencies
Upgrade project dependencies with breaking change research for major version updates. Use when the user asks to "update dependencies", "upgrade packages", "upgrade dependencies", "update deps", "upgrade deps", "update npm deps", "update Swift packages", "cargo update", "go get updates", "bundle update", or "pip upgrade".
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
-
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
-
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