commit
Use when the user asks to commit/save staged or unstaged changes with a repo-appropriate, value-communicating message.
commit-push
Use when asked to ship/publish commits without opening a PR.
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.
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.
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".
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.
github-solution-research
Find open-source solutions on GitHub. Use when facing a bug, integration failure, dependency issue, unclear API usage, implementation blocker, or tool capability need.
github-triage
Triage GitHub issues. Use when the user wants to triage incoming issues, prepare issues for an autonomous agent, or move an issue between workflow states.
handoff
Snapshot the current session into a resumable handoff artifact so a cold session, agent, or person continues without replaying context. Use when the user says "write a handoff", "hand off", "snapshot this session", "I'm running low on context", "pause and pack this up for the next session", or "resume this later".
ideate
Generate grounded, divergent ideas from the codebase. Use when the user says "let's brainstorm", "what should we build", or "any ideas for".
improve-architecture
Surface deepening refactors that turn shallow modules into deep ones. Use when the user asks to improve architecture, find refactor candidates, raise testability, or make a codebase more agent-navigable.
incremental
Use when a change spans multiple files, or you're about to write a lot of code at once.
llm-self-loop
Restructures human-gated workflows into autonomous LLM loops with file-based outputs. Use when a task needs a button click, dashboard check, or human verdict inside its iteration loop.
loop-me
Use when the user wants to design a recurring personal or team workflow: capture loops, write specs in workflows/*.md, and run a stateful askme session until the spec is implementer-ready. Triggers: "loop me", "design a workflow", "automate this recurring task", morning routine, inbox processing.
memory-clean
Use when the user asks to audit memory or find stale or duplicate memories.
memory-sanitize
Use when sanitizing memory for sharing, redacting PII, or scanning for credentials.
memory-update
Use when the user says save this to memory, or scan this session for memories.
minimalism-driven
Build the smallest version that fully does the job and makes its intent obvious — the right amount, not the fewest lines. Use when scope creep, speculative abstraction, or unneeded surface is a risk; before adding a helper, wrapper, config key, or dependency; or when the user says "minimal", "DRY this up", or "no gold-plating".
mutual-sync
Use when user, agent, and codebase may hold different pictures of the current state: before substantive work after a gap, or mid-session when parties talk past each other. Triggers: "mutual sync", "sync up", "are we on the same page", stale user claims about the code, refuted agent assumptions.
observability
Instrument code with structured logs, metrics, and traces. Use when adding telemetry, setting up or reviewing alerting rules, shipping a production feature, or diagnosing opaque production issues.
onboard
Use when the user asks to be onboarded, oriented, given a tour, or shown where to start in a repo.
optimize
Use when the user asks to optimize something, reduce allocations, or fix a performance regression.
parallel-launch
Use when the request has multiple independent sub-tasks, cross-domain research, or parallelizable file or module work.
pov
Verdict on whether to adopt, switch to, or revisit a technology, library, pattern, platform, or architecture; also a mid-session second opinion. Use for a verdict against the current project, not for neutral explainers or option-generation.
pr-merge-base
Use when PRs may conflict with each other or the base, or require ordered application.
pr-merge-temporal
Use when validating a set of PRs together on a staging branch before advancing the base branch.
pr-review
Use when the user asks to review a pull request, or wants structured quality, security, and testing feedback on a PR diff.
refactor-break-compat
Use when modernizing APIs, removing compat shims, killing feature flags, or rewriting a subsystem cleanly.
research
Use when researching a named library, framework, SDK, API, or service, or finding a migration guide.
resolve-pr-feedback
Use on a GitHub PR when addressing review comments or resolving review threads.
review
Use when reviewing current work or recent commits, or running a deep review.
review-fix-grill-loop
Use when the user says "grill my changes" or wants their diff reviewed and fixed iteratively until clean.
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.
Page 806 of 1671 · 83537 results
