process-review
Process review comments in a file after user finishes reviewing in file-review GUI. Extracts HTML comment markers, guides Claude through addressing each comment interactively, and removes resolved markers.
- Installs
- 38
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/desplega-ai/ai-toolbox --skill process-review- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads process-review automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Process Review Comments
Thin redirect. Follow the Process Comments section of the file-review:file-review skill for full instructions.
FAQ
What does the process-review skill do?
Process review comments in a file after user finishes reviewing in file-review GUI. Extracts HTML comment markers, guides Claude through addressing each comment interactively, and removes resolved markers.
How do I install process-review?
Run npx skills add https://github.com/desplega-ai/ai-toolbox --skill process-review in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/process-review/ (personal) or .claude/skills/process-review/ (project).
Which AI agents can use process-review?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is process-review safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains process-review?
It is published by desplega-ai in desplega-ai/ai-toolbox. It has 38 recorded installs.
More from desplega-ai/ai-toolbox
researching
desplega-ai/ai-toolbox
Comprehensive codebase research skill. Documents codebase as-is by spawning parallel sub-agents and synthesizing findings into research documents.
planning
desplega-ai/ai-toolbox
Implementation planning skill. Creates detailed technical plans through interactive research and iteration.
tdd-planning
desplega-ai/ai-toolbox
TDD-focused implementation planning. Creates plans with strict Red-Green-Commit/Rollback cycles for each step.
implementing
desplega-ai/ai-toolbox
Plan implementation skill. Executes approved technical plans phase by phase with verification checkpoints.
wts-expert
desplega-ai/ai-toolbox
Git worktree management expert for @desplega.ai/wts. Use when the user asks about git worktrees, wts commands, worktree workflows, or wants help managing multiple branches simultaneously.
ask-user
desplega-ai/ai-toolbox
Conventions for asking the user questions during a workflow via the AskUserQuestion tool. Other skills reference this to keep prompts consistent and structured.
Popular code quality & workflow skills
grill-me
mattpocock/skills
A relentless interview to sharpen a plan or design.
improve-codebase-architecture
mattpocock/skills
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
handoff
mattpocock/skills
Compact the current conversation into a handoff document for another agent to pick up.
domain-modeling
mattpocock/skills
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
codebase-design
mattpocock/skills
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.