review-fix-grill-loop
Use when the user says "grill my changes" or wants their diff reviewed and fixed iteratively until clean.
review
Use when reviewing current work or recent commits, or running a deep review.
security-hardening
Harden code against vulnerabilities as you build it. Use when handling untrusted input, authentication or authorization, data storage, or external integrations.
security-review
Run an adversarial security audit using STRIDE, OWASP, supply-chain checks, secrets scans, and auth analysis. Use when changes touch auth, input parsing, dependencies, or network I/O, or before a production release.
setup-gitignore
Use when the user says "set up gitignore", "fix gitignore", or untracked files keep appearing in git status.
setup-pre-commit
Use when the user wants commit-time checks, or says "install husky/pre-commit/lefthook".
setup-ts-deep-modules
Wire dependency-cruiser into a TypeScript repo so each package is a deep module: implementation hidden in subfolders, reachable only through its entry-point files. Use when the user asks to enforce package boundaries, set up deep modules, stop deep imports, or wants code outside a package to import only its entry points.
shipping
Use when deploying to production, planning a feature release, or setting up launch safeguards.
simplify
Use when the user says "simplify this diff", or asks for a compression pass over a change-set.
ai-collab-protocols
Surface in-task AI collaboration protocols one tactic at a time. Use when the user refers to entities by colloquial labels, asks how to structure a Claude workflow, or describes a multi-step workflow without durable URLs.
api-design
Guide stable API and interface design. Use when creating REST or GraphQL endpoints, defining type contracts, or establishing frontend/backend or module boundaries.
askme
Explore intent with Verbalized Sampling before planning. Use when the task is ambiguous, you need maximum clarifying questions, or you want collaborative or adversarial mode via `/askme`.
ast-grep
Run code analysis and refactoring with ast-grep. Use when doing AST-based modifications, structural search, linting across code shape, or replacing regex-fragile transformations.
atomic-issues-prs
Publish a change-set as atomic GitHub issues or PRs. Use when the user says "atomic PRs" or wants one issue/PR per logical change.
audit-project
Run an iterative multi-agent code audit until critical and high findings are resolved. Use when the user says "audit my code", "find all the bugs", "deep code audit", "iterative review", or "review until clean".
autolearn
Compound a solved problem into a durable in-repo learning doc. Use when a verified non-trivial fix lands, the user says "compound this", "document this fix", or "remember this".
autopilot
Run a hands-off plan-to-ship pipeline by chaining existing skills. Use when the user says "autopilot", "take this from plan to shipped", "run the whole pipeline", "hands-off ship it", or "do the end-to-end build".
axiom-mode
Switch to ODIN's compact formal-logic English register using predicate claims and ASCII keywords. Use when the user requests "axiom", "axiom-mode", "axiom-compact", "formal-logic", or "compact form".
batch-ask-me
Use when the user wants to walk a complex design space round by round: map the decision tree, fire the current frontier as batched single-select questions, and loop until shared understanding is reached. Triggers: multi-fork decisions, ambiguous requirements, unresolved prerequisites, "batch ask me", "clarify the design space".
brainstorm
Explore vague or ambitious ideas into a right-sized requirements-only plan. Use when the user wants to brainstorm, think through scope, decide what to build, or needs collaborative product framing before planning, not for a decisive verdict on whether to adopt or switch to a specific external technology, library, or platform.
breaking-driven
Demolish bloated code and re-derive it clean, cutting every surface the rebuilt contract does not name. Use for a repo-wide bloat sweep, when patching a subsystem has stopped paying, or when the user says "this whole module is bloated", "rewrite this properly", or "break it and rebuild".
browser-testing
Test and debug browser code with Chrome DevTools MCP. Use when building or debugging browser UI, inspecting the DOM, capturing console errors, analyzing network requests, or verifying visual output.
can-i-help
Route contributors to data-backed contribution opportunities. Use when the user asks "where can I help", "what can I contribute", "find a good first issue", or "what should I work on".
caveman
Switch to a verbosity-reduction response register. Use when the user says "caveman", "compact mode", "less tokens", "be brief", or context-window pressure calls for shorter replies.
ci-cd
Set up or modify CI/CD pipelines and deployment automation. Use when setting up build pipelines, automating quality gates, configuring test runners in CI, or establishing deployment strategies.
cleanup-codebase
Reduce internal duplication, dead code, and ceremony. Use when you spot dead fields, redundant wrappers, or speculative abstractions in code you are already editing.
commit-push-current
Commit working-tree changes and push to the current branch: no branch creation, no branch switch, no PR. Use when asked to push to the branch you are already on, including the default branch.
commit-push-pr
Use when asked to ship/open a PR, or for PR-description-only flows like writing, rewriting, or describing a PR body.
commit-push
Use when asked to ship/publish commits without opening a PR.
commit
Use when the user asks to commit/save staged or unstaged changes with a repo-appropriate, value-communicating message.
compound
Use when the user says "compound this", after a verified non-trivial outcome that should live in docs/solutions/ or CONCEPTS.md, or when a durable project term needs defining.
contexts
Use when the user says "get context on X", "how does X work", or wants architectural orientation before coding.
contract-driven
Design-by-Contract (DbC). Use when crossing public API boundaries, guarding complex state invariants, or hardening untrusted inputs and integration seams.
debug
Hypothesis-driven debugging. Use when a test fails, a crash or exception occurs, output is wrong, or an intermittent flake has no obvious cause.
deprecate-and-migrate
Use when removing old code, migrating users to a new implementation, or deciding whether to maintain or sunset something.
deps-upgrade
Dependency-upgrade campaign. Use when CVEs require remediation, a major upstream version lands, stack compatibility forces a sweep, on a scheduled hygiene cadence, or for a lockfile audit before a release.
design
Use when starting UI work, defining palettes or design tokens, or when output looks AI-generic, vibe-coded, or default-framework sloppy.
deslop
Use when the user says "deslop", "remove debug code", "find placeholders or stub code", or "remove dead code".
doc-review
Use when the user asks to review or critique a prose planning document — a plan, spec, PRD, requirements doc, or design doc.
docs-and-adrs
Document decisions, not just code. Use when making architectural decisions, changing public APIs, shipping features, or capturing context for future engineers and agents.
doubt-driven
Doubt-driven adversarial review. Use when correctness matters more than speed, the code is unfamiliar, stakes are high, a claim can't be checked by the type system or compiler, or verifying now is cheaper than debugging later.
drift-detect
Use when the user says "plan drift", asks whether the roadmap, plans, or docs still match the code, or is deciding what to rebuild when restarting a stalled project.
duet
Use when the user invokes /duet, says "pair with me", or faces aesthetic, architectural, or irreversible decisions.
enhance
Audit and tighten agent/plugin surfaces. Use when the user asks to enhance a plugin config, agent definition, skill, or CLAUDE.md.
explore
Explore the codebase to map structure, symbols, and dependencies. Use when the user says "explore", "find where X is", "how does X work in the code", or "map the codebase".
fix
Use when the user says "fix", "make it pass", or "apply the findings", or hands a verifier failure or bug description.
frontend-ui
Build user-facing interfaces. Use when creating or modifying components, implementing layouts, managing state, or when the output must look hand-crafted rather than AI-generated.
generate-my-taste
Generate a personal taste skill from local evidence and confirmation forks. Use when the user says "generate my taste skill", "make my taste skill", or "derive my taste spine".
gh-fix-ci
Use when the user asks to debug or fix failing CI checks on a GitHub pull request.
git-branchless
Use when doing multi-commit work, stack edits, rebases, fixups, stacked-PR publishing, or when the user mentions branchless, smartlog, git move, or git undo.
Page 1 of 3 · 101 results