critique — Claude Code skill: multi-judge review of finished work
The critique skill runs finished work past several AI judges: they review it independently, debate their findings, and agree on a shared list of issues.
npx skills add NeoLabHQ/context-engineering-kit --skill critique -a claude-codeWhat critique does
The critique skill reviews work you have already completed. A coordinator gathers the context — the original request, changed files, decisions made along the way — and spawns three judges in parallel through the Task tool. One checks alignment with the requirements, one weighs the chosen approach against alternatives, one looks at code quality and refactoring spots.
Each judge works alone first, then asks itself verification questions and revises its verdict based on the answers. After that the judges debate their findings and settle on agreed recommendations. The whole thing is report-only: the skill changes nothing, it hands the findings to you.
Pass no arguments and it falls back to the conversation history and recent file changes; if the scope is fuzzy it asks what to review. Runs in Claude, Codex, Cursor, GitHub Copilot, Gemini CLI and OpenCode.
What it helps with
- check whether every part of the original request was actually done
- surface places where the approach could have gone another way
- get a list of code issues without touching the code
- separate missed requirements from scope creep
- collect a second opinion on a fresh change before committing
Example prompts for the agent
- Run critique on the changes in
src/auth/session.ts - Critique the last commit and show what's still open from the task
- Run critique over all the work in this conversation
How to install critique
1Skills CLI (Vercel)
npx skills add NeoLabHQ/context-engineering-kit --skill critique -a claude-code2Manually: put the files in place
~/.claude/skills/critique/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/critique/
1Skills CLI (Vercel)
npx skills add NeoLabHQ/context-engineering-kit --skill critique -a codex2Manually: put the files in place
.agents/skills/critique/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add NeoLabHQ/context-engineering-kit --skill critique -a cursor2Manually: put the files in place
.cursor/skills/critique/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install NeoLabHQ/context-engineering-kit critique2Manually: put the files in place
.github/skills/critique/SKILL.md1Skills CLI (Vercel)
npx skills add NeoLabHQ/context-engineering-kit --skill critique -a gemini-cli2Platform CLI
gemini skills install https://github.com/NeoLabHQ/context-engineering-kit --path skills/critiqueManually: put the files in place
.devin/skills/critique/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add NeoLabHQ/context-engineering-kit --skill critique -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about critique
How do I install critique in Claude?
Run npx skills add NeoLabHQ/context-engineering-kit --skill critique -a claude-code. The skill file then lands at ~/.claude/skills/critique/SKILL.md.
What does critique do?
It puts finished work through three independent judges: a requirements check, an approach review and a code quality pass. The judges debate and return one combined report of findings.
Does critique fix the code itself?
No. It reads and reports only, leaving the findings for you. You apply the fixes yourself or hand them to the agent as a separate task.