Review
Run an adversarial code review on staged changes or a specific file. Spawns the code-critic agent to find bugs, performance issues, and missed edge cases. Use before merging PRs or committing.From its SKILL.md
npx -y skills add fullymiddleaged/Clawness --skill reviewAssembled 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
1.4 KB, as published. Nobody here has run it
Adversarial Code Review
Run a thorough code review using the Clawness code-critic agent.
Before spawning the agent: if you surfaced this proactively (the user mentioned reviewing/merging but didn't explicitly ask to run it), first ask: "Want me to run the adversarial code review now?" Proceed only once they confirm. If the user explicitly invoked
/clawness:reviewor already said yes, skip the question.
Steps
-
Identify changes — If $ARGUMENTS specifies files, review those. Otherwise, check for staged git changes (
git diff --cached). If nothing is staged, review the most recently changed files (git diff HEAD~1). -
Delegate to code-critic — Send the relevant code to the
code-criticsub-agent for adversarial review focusing on:- Correctness bugs and logic errors
- Performance issues (N+1, re-renders, memory leaks)
- Missing edge cases (null, empty, concurrent, malicious)
- Maintainability (naming, complexity, duplication)
-
Report — Present findings grouped by severity. For each finding, include the file, line, problem, and suggested fix.
-
Offer to fix — Ask the user if they want to apply any of the suggested fixes.