Critique
Critique all unpushed commits before pushing to remoteFrom its SKILL.md
npx -y skills add RobinNorberg/oh-my-copilot --skill critiqueAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
5.5 KB, as published. Nobody here has run it
<Use_When>
- Before pushing commits: "critique my changes", "review before push",
/critique - When you want a second opinion on uncommitted or unpushed work
- As a pre-PR quality gate
- When Claude has been writing code and you want an independent check </Use_When>
<Do_Not_Use_When>
- Reviewing a PR that's already pushed — use
/revieworcode-revieweragent instead - Deep multi-pass review needed — use
/deep-reviewinstead - Only want security review — use
security-revieweragent directly </Do_Not_Use_When>
<Why_This_Exists> Claude writes code confidently. Too confidently. Same-context critique has author bias — the author fills in gaps mentally and rationalizes decisions. An independent subagent only sees the artifact and the codebase, catching flaws the author is blind to. This is the last line of defense before code reaches the remote. </Why_This_Exists>
<Execution_Policy>
- The devils-advocate agent MUST run as an independent subagent (Task), never inline — this prevents author bias
- Agent is read-only (Write/Edit blocked)
- Agent uses opus model for thoroughness (user can override via config)
- Results are presented to the user with a clear PUSH / FIX FIRST recommendation </Execution_Policy>
-
Gather context (run in parallel):
- Commit log:
git log <range> --format="%h %s" - Changed files summary:
git diff <range> --stat - Full diff:
git diff <range> - If the full diff exceeds ~3000 lines, use
git diff <range> --statplus targetedgit diff <range> -- <file>for the most critical files (prioritize: security-sensitive, core logic, new files)
- Commit log:
-
Spawn independent devils-advocate agent:
Task(subagent_type="oh-my-copilot:devils-advocate", model="opus", name="critique", prompt=" INDEPENDENT PRE-PUSH CRITIQUE Review the following unpushed commits for flaws, suboptimal code, insufficient implementation, faults, and broken behavior. You are an independent reviewer — the author cannot see your investigation process, only your final report. ## Commits [paste commit log here] ## Changed Files [paste diff stat here] ## Full Diff [paste diff here] Produce a structured Pre-Push Critique report with PASS/FAIL for each criterion, file:line citations and proposed fixes for every FAIL, and a clear PUSH or FIX FIRST recommendation. ") -
Present results: Display the structured critique report to the user exactly as returned by the agent.
-
Ask the user: Based on the recommendation:
- If PUSH: "The critique found no blocking issues. Proceed with push?"
- If FIX FIRST: "The critique found issues that should be fixed before pushing. Would you like to address them or push anyway?" </Steps>
<Tool_Usage>
- Use Bash with
git logandgit diffto gather commit and diff data - Use
Task(subagent_type="oh-my-copilot:devils-advocate", ...)to spawn the independent reviewer - Do NOT run the critique inline — it MUST be a separate subagent for independence </Tool_Usage>
<Output_Format> [Display the full Pre-Push Critique report from the devils-advocate agent]
Recommendation: PUSH / FIX FIRST [If FIX FIRST, list the critical FAILs that need attention]
Proceed with push, or fix the issues first? </Output_Format>
<Final_Checklist>
- Unpushed commits detected (or user-provided range used)
- Full diff gathered (or targeted diffs for large changesets)
- Independent devils-advocate agent spawned (NOT inline review)
- Structured report with PASS/FAIL per criterion presented
- Every FAIL has file:line citation and proposed fix
- Clear recommendation issued (PUSH / FIX FIRST)
- User asked how to proceed </Final_Checklist>