
Discuss design decisions, trade-offs, and technical ideas — system design, API design, architecture, refactoring strategy, feature approach, or any 'how should I structure/approach this' question.
--- name: commit-msg description: "Generate a conventional commit message from staged changes and copy to clipboard." allowed-tools: Bash(pbcopy:*), Bash(git diff:*), Bash(git log:*), Bash(git branch:*), Bash(gh:*), Bash(glab:*) argument-hint: [hint] [--pr] --- ## Context - Branch: !`git branch --show-current` - Staged diff: !`git diff --cached` - Recent commits: !`git log --oneline -10` ## Rules - If there are no staged changes (empty diff above), say so and stop - **ONLY use the staged diff
--- name: docs description: "Audit and fix documentation drift — stale docstrings, missing docs on public APIs, outdated README sections. Spawns the doc-auditor agent." allowed-tools: Read, Glob, Grep, Edit, Write, Bash(git diff:*), Bash(git branch:*) argument-hint: [file/dir|staged|all] [--dry-run] --- ## Context - Branch: !`git branch --show-current` - Changed files: !`git diff --name-only HEAD` ## Task Audit documentation for the specified target by spawning the `doc-auditor` agent. ### T
Guided feature development — explores codebase, clarifies requirements, designs approach, implements with review gates. Use for substantial new features.
Temporarily protect files/directories from edits during a session. Use to prevent accidental changes to files outside current scope. /freeze <paths> to lock, /freeze --list to show, /freeze --clear to unlock all.
--- name: refactor description: "Identify and apply refactoring opportunities — supports full analysis, cleanup, simplify, structure, naming, and DRY focus modes." allowed-tools: Read, Glob, Grep, Edit, Write, Bash(git diff:*), Bash(git branch:*) argument-hint: [file/dir|staged] [full|cleanup|simplify|structure|naming|dry] --- ## Context - Branch: !`git branch --show-current` - Changed files: !`git diff --name-only HEAD` - Diff stats: !`git diff --stat HEAD` ## Task Analyze code for refactori
This skill should be used when the user says 'remember this', 'save this for later', 'note this down', 'always do X', 'never do Y', or wants to persist a decision or preference across sessions.
--- name: review description: "Code review — detects language and spawns the appropriate reviewer agent. Works with diffs, staged changes, files, or directories." allowed-tools: Read, Glob, Grep, Edit, Write, Bash(git diff:*), Bash(git log:*), Bash(git status:*), Bash(git branch:*) argument-hint: [file/dir|staged|lang] [security|performance|idioms|bugs|tests] [--fix] [--deep] --- ## Context - Branch: !`git branch --show-current` - Changed files: !`git diff --name-only HEAD` - Diff stats: !`git
Analyze test coverage gaps — untested public APIs, missing edge cases, uncovered error paths. Spawns the test-analyzer agent.
--- name: qa description: "Run QA on the current project. Auto-detects project type and runs browser testing for frontend projects. Use after implementing features to verify they work end-to-end." allowed-tools: Read, Glob, Grep, Bash(bun run:*), Bash(npm run:*), Bash(curl:*), Bash(lsof:*), Bash(kill:*), mcp__plugin_playwright_playwright__* argument-hint: [url or flow to test] [--fix] --- ## Task Verify the project works end-to-end by running it and testing interactively. Not a code review — t
Reflect on the current session and extract reusable patterns worth remembering. Use when a session involved mistakes, corrections, debugging breakthroughs, or workarounds that should inform future sessions.
Clean up local branches marked as [gone] and their associated worktrees
UI/UX design critique before building. Describe what you want, get feedback on layout, flow, accessibility, and patterns. Use before implementing frontend features.