Menu
Add documentation comments to all changed code files, dispatching one agent per file.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Take an iteration and execute it: dispatch /implement agents per phase, always sequentially (e.g. /orchestrate <iteration-id>).
Take an iteration and execute it: dispatch /implement agents per phase with git worktree isolation for parallel work (e.g. /orchestrate <iteration-id>).
Take an iteration and execute it: dispatch /implement agents per phase with jj workspace isolation for parallel work (e.g. /orchestrate <iteration-id>).
Promote a gest task to a GitHub Issue (e.g. /promote-task <id>).
Explore a rough idea with the user, clarify requirements, and draft a spec. Also decomposes large specs into smaller ones (e.g. /brainstorm "offline mode", /brainstorm <gest-id>).
Implement a single issue: write code, verify, review, format, and commit (e.g. /implement <gest-id>).
| name | doc-code |
| description | Add documentation comments to all changed code files, dispatching one agent per file. |
Add documentation comments to all changed code files in the current diff.
Run git diff --name-only to identify changed files. Filter the list to only include source code files (e.g., *.rs,
*.ts, *.py — exclude non-code files like *.md, *.toml, *.lock, *.json, *.yaml).
For each changed source code file, dispatch an agent to document that file. Launch all agents in parallel.
Each agent should:
git diff <file_path> to see exactly which lines were added or modified./// and //! for Rust, /** */ or // for TypeScript,
""" docstrings for Python)./// Returns the name on a method called name()).Run mise lint to verify that the added documentation does not introduce any lint errors.
Run mise test to confirm nothing is broken.