Loading...
Loading...
Found 10,340 Skills
Critique-and-rewrite enforcement loop for voice fidelity. Validates generated content against negative prompt checklists and forces revision until it passes. Use when content has been generated in a target voice, voice output feels off, long-form content risks voice drift, or before final delivery of voice content. Use for "validate voice", "check voice", "voice feels wrong", "voice drift", or "rewrite for voice". Do NOT use for initial voice generation, voice profile creation, or content that has no voice target.
Sync local changes to GitHub in one command: detect state, branch, commit, push, create PR. Use when user wants to push work to GitHub, create a PR, or sync a feature branch. Use for "push my changes", "create a PR", "sync to GitHub", "open pull request", or "ship this". Do NOT use for reviewing PRs (use /pr-review), cleaning up after merge (use pr-cleanup), or CI checks (use ci).
Zero-ceremony inline execution for tasks completable in 3 or fewer file edits. No plan, no subagent, no research — just understand, do, commit, log. Use for "quick fix", "typo fix", "one-line change", "trivial fix", "rename this variable", "update this value", "fix this import". Do NOT use for tasks requiring research, planning, new dependencies, or more than 3 file edits — redirect to /quick instead.
Systematic 6-phase analysis of external repositories for ideas worth adopting: clone, parallel deep-read, self-inventory, synthesize gaps, targeted audit of affected subsystems, reality-grounded report. Use when evaluating whether an external repo provides value, analyzing repos for useful patterns, or comparing approaches. Do NOT use for general codebase exploration (use explore-pipeline instead).
Generate and validate Git branch names from commit messages or descriptions. Use when creating branches, generating names for /pr-sync, validating existing branch names, or converting conventional commits to branch prefixes. Triggers: "branch name", "create branch", "name this branch", "validate branch". Do NOT use for git operations (checkout, merge, delete), branching strategies, or branch protection rules.
Resolve all pending CLI todos using parallel processing, compound on lessons learned, then clean up completed todos.
Refresh stale or drifting learnings and pattern docs in docs/solutions/ by reviewing, updating, replacing, or archiving them against the current codebase. Use after refactors, migrations, dependency upgrades, or when a retrieved learning feels outdated or wrong. Also use when reviewing docs/solutions/ for accuracy, when a recently solved problem contradicts an existing learning, or when pattern docs no longer reflect current code.
Verifies user credentials on Moca chain testnet via AIR agent sessions. Use when a user wants to verify a credential, list available verification programs, or check credential compliance.
Sync design tokens between code and Figma variables with strict drift reporting, mandatory approval gate, safe delta apply, and persisted reports.
Execute and implement approved specification proposals in sequence with testing and verification as the priority. It is used for implementing changes, applying proposals, executing specification tasks, or building according to approved plans. Trigger words include "openspec development", "development", "implementation", "implement proposal", "apply change", "execute specification", "complete tasks in order", "build feature", "start implementation"
CLI reference for worker agents — how to claim tasks, log progress, submit for review
Suggest what to work on next based on project state and session context. Considers proximity, momentum, status, and constraints.