jamesc
19 verified skills
resolve-pr
Address PR review comments systematically. Use when user types /resolve-pr or asks to fix/address PR feedback, review comments, or requested changes.
documentation
pick-epic
Execute an epic by running children in dependency-ordered waves using parallel subagents, one isolated worktree and PR per issue, squash-merging as CI and automated reviews (CodeRabbit + Copilot) pass. Use when user types /pick-epic or asks to execute an epic with parallel agents.
development
done
Complete work and push changes. Use when user types /done or says they are finished with the current task and ready to commit/push/create PR.
tools
draft-adr
Research a problem and draft an Architecture Decision Record. Use when user asks to design/draft/write an ADR or make an architectural decision.
testing
resolve-merge
Update main branch, merge into current branch, and resolve conflicts. Use when user types /resolve-merge or asks to merge main/resolve conflicts.
data-ai
update-issues
Find and update Linear issues that need labels, blocking relationships, or metadata. Use when user says '/update-issues' with criteria like 'no labels', 'missing agent-ready', 'needs size', etc.
data-ai
plan-refactor
Analyze the codebase and plan refactoring for code quality and maintainability. Use when user types /plan-refactor or asks to plan refactoring work.
development
linear
Manage Linear issues. Use when asked about tasks, tickets, bugs, or Linear.
tools
sync-skills
Sync modified skills and agents back to the repo and create a PR. Use when user types /sync-skills or wants to save in-session skill improvements.
data-ai
refresh-issue
Refresh a Linear issue to align with current docs and code state. Use when user types /refresh-issue BT-XX or asks to refresh/sync an issue with the codebase.
development
do-refactor
Execute a refactoring epic on a single branch, implementing all issues sequentially with CI verification after each. Use when user types /do-refactor or asks to execute a refactoring plan.
development
whats-next
Find the next logical piece of work. Use when user types /whats-next or asks what they should work on next, or wants recommendations for the next task.
tools
review-code
Review current branch changes vs main. Use when user types /review-code or asks for a code review of their changes.
development
review-adr
Review an Architecture Decision Record for completeness, correctness, and quality. Use when user types /review-adr or asks to review an ADR.
testing
create-issue
Create a Linear issue with proper structure and blocking relationships. Use when creating new tasks, breaking down work, or setting up dependencies between issues.
testing
explain
Create a walkthrough document for code, a pattern, or a feature. Prompts the user for walkthrough style (demo, linear, architecture, API reference, ...) and produces the appropriate document using showboat or plain markdown.
development
pick-issue
Start working on next Linear issue. Use when user types /pick-issue or asks to pick up the next task from the backlog.
tools
plan-adr
Break an accepted ADR into implementation issues with an Epic. Use when user types /plan-adr or asks to plan implementation of an ADR.
tools
use-lsp
Use when navigating code, finding references, looking up definitions, understanding types, or tracing call hierarchies in TypeScript, Rust, or Beamtalk (.bt) files. Prefer LSP over Grep/Glob for any navigation task where symbol semantics matter.
development