Loading...
Loading...
Found 8,194 Skills
Follow this sub-process when fixing bugs — turn the verbal description of "problem found" into a closed loop from verification to repair, leaving three documents: problem report, root cause analysis, and repair record. This process adds a buffer between "seeing the problem" and "starting to modify code" to avoid common pitfalls: the problem description in your mind disappears after the fix, you only fix the surface without analyzing the root cause, the scope of repair expands and cannot be traced, and you don't know if the fix is correct without verification after modification. This skill only acts as a router, deciding which of report / analyze / fix to proceed with based on existing artifacts. For simple problems that can be identified at a glance, a fast track will be taken, skipping the two middle steps and only retaining the fix-note.
Enter this sub-process when conducting code optimization — handle tasks where 'behavior remains unchanged, structure changes' (structure / performance / readability). Shift single-module internal optimization from 'AI random refactoring' to 'first scan to generate a checklist, confirm each item with the user, execute step-by-step according to the method library, and require manual approval for each step'. Trigger scenarios: Users mention phrases like 'optimize it / refactor / rewrite / split it / poor performance / code is too long' without any accompanying behavior changes. Do not handle new requirements (route to feature), bugs (route to issue), or cross-module architecture restructuring (route to architecture + decisions).
Generate structured planning docs for web projects with context-safe phases, verification criteria, and exit conditions. Creates IMPLEMENTATION_PHASES.md plus conditional docs. Use when: starting new projects, adding major features, or breaking large work into manageable phases.
Manage tasks via dex CLI. Use when breaking down complex work, tracking implementation items, or persisting context across sessions.
This skill is for interacting with Anki through AnkiConnect, and should be used whenever a user asks to interact with Anki, including to read or modify decks, notes, cards, models, media, or sync operations.
Bootstrap lean multi-agent orchestration with beads task tracking. Use for projects needing agent delegation without heavy MCP overhead.
Interactive Intent approval. Review sections and mark status (locked/reviewed/draft). Use /intent-review <path> to review a specific file, or /intent-review to review Intent in current directory.
Assess if IDD fits your project and learn about Intent-Driven Development. Use /intent-assess to evaluate project suitability or /intent-assess --learn for IDD education.
Start implementation from Intent. Validates Intent completeness, then either delegates to TaskSwarm (if available) or executes TDD phases directly. Use when you have an Intent ready and want to start building.
Set up automated agent-driven development with Ralph. Run AI agents in a loop to implement features from user stories, verify acceptance criteria, and log progress for the next agent.
Merges GitHub Pull Requests after validating pre-merge checklist. Use when user wants to merge PR, close PR, finalize PR, complete merge, approve and merge, or execute merge. Runs pre-merge validation (tests, lint, CI, comments), confirms with user, merges with proper format, handles post-merge cleanup.
Set up and run Ralph Wiggum loop - autonomous AI coding with clean slate iterations, PRD-driven features, and CI quality gates. Use for long-running autonomous coding tasks.