Agent Claude Code
You are reviewing code changes for production readiness.
Agent Claude Code
You are reviewing code changes for production readiness.
Agent Claude Code
Reviews implementation plans for completeness, risks, and codebase alignment. Use after writing a plan and before executing it.
Command Claude Code
Archive completed projects, write a monthly work summary.
Command Claude Code
Close out a project (active) or plan (evergreen) with task triage, findings extraction, and changelog summary.
Command Claude Code
Brainstorm scope and create a new project.
Command Claude Code
Execute an implementation plan task-by-task with review checkpoints.
Command Claude Code
Set a descriptive name for the current tmux window.
Command Claude Code
Append a note, link, or discovery to today's daily note.
Command Claude Code
Create implementation plan with bite-sized tasks.
Skill Claude CodeCodex
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Skill Claude CodeCodex
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies.
Skill Claude CodeCodex
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available.
Skill Claude CodeCodex
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work.
Skill Claude Code
Use when the user invokes /neovim-review for a pull request or a local :Review session in Neovim.
Skill Claude Code
Interact with a running neovim instance over RPC — open files, show diffs, execute Lua. Use when you need to open a file in the user's editor, show a vimdiff, or run arbitrary Lua in neovim. Requires $NVIM or $NVIMSOCKETPATH to be set.
Skill Claude CodeCodex
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation.
Skill Claude CodeCodex
Use when completing tasks, implementing major features, or before merging to verify work meets requirements.
Skill Claude CodeCodex
Use when executing implementation plans with independent tasks in the current session.
Skill Claude CodeCodex
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
Skill Claude CodeCodex
Use when implementing any feature or bugfix, before writing implementation code.
Skill Claude CodeCodex
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback.
Skill Claude CodeCodex
Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions.
Skill Claude CodeCodex
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always.
Skill Claude CodeCodex
Use when you have a spec or requirements for a multi-step task, before touching code.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: