Review AI-authored code for its characteristic failure modes — plausible-but-wrong logic, hallucinated APIs, over-engineering, dead scaffolding, and silent security shortcuts. Use when reviewing an AI-generated or heavily AI-assisted PR, when AI-written code keeps shipping subtle bugs, or when setting review standards for a team using coding agents. Produces a focused review with AI-specific findings, verification steps per risk class, and a team checklist for AI-authored changes. For general PR review use code-review-checklist — this skill covers what that one assumes a human wouldn't do.
“Review this AI-generated pull request.”“Claude wrote this code: what did it get wrong?”“Check this PR for hallucinated APIs.”“Set review standards for a team using coding agents.”
What to give it
▸The diff or PR — or the files changed
▸Provenance honestly — fully agent-written, human-piloted, or mixed — and whether the *author reviewed it themselves* before requesting review
▸The codebase context — existing conventions/utilities the AI may not have known, and what the change claims to do
▸Test infrastructure — what CI actually runs (the AI may have written tests CI never executes)
✅ The bar it holds itself to
Every skill in this library self-verifies — these are this skill's own quality checks, straight from its definition.
✓At least one concrete input was hand-traced through the changed logic
✓Every touched external API was verified against the actual dependency version
✓Each test was assessed by "what breakage would this catch?"
✓New helpers were grepped against existing utilities
✓The verdict distinguishes required fixes from accepted debt
⚠️ What it refuses to do
Do not extend human-code trust heuristics ("clean and well-named, so probably correct") — fluency is the failure mode's costume
Do not approve on green CI without checking whether the tests can fail
Do not review the description instead of the diff — AI PR descriptions are confident summaries of intent, not of behaviour
Do not reject code *for being* AI-written — review the code; provenance calibrates scrutiny, not verdicts
Do not skip security linting because the change is small — the shortcut hides in the periphery
Install
npx pm-claude-skills add --agent claude # or codex · cursor · gemini · hermes
# or one-line MCP (every skill, any client):
claude mcp add pm-skills -- npx -y -p pm-claude-skills pm-claude-skills-mcp