review-changes

Changes under review

git status --short --branch
git diff --stat HEAD
git log --oneline -5

Task

Review these changes. Start by running git diff (and git diff <base>...HEAD for the full branch, where <base> is the branch this will merge into) so you are reviewing the actual content, not just the summary above. Launch both reviewers in parallel — they are independent:

• code-reviewer — quality, patterns, maintainability.
• security-reviewer — OWASP Top 10, secrets, injection, authz, information disclosure.

Both ship with this plugin, so they may be namespaced as claude-standards:code-reviewer and claude-standards:security-reviewer. Use whichever form your agent list actually shows.

Add a language-specific reviewer only if it is already defined — as a project agent, or as one listed in this plugin's roster. Do not invent a reviewer name and hope it resolves; if the agent does not exist, say so and review that dimension yourself rather than silently skipping it.

While the agents run, check the mechanical gates yourself:

• Automated checks pass (lint, types, tests) and coverage is ≥80%.
• No merge conflicts; branch is up to date with its target.
• No leftover debug statements (print, console.log) or commented-out code.
• No hardcoded secrets, keys, or tokens anywhere in the diff.

Output

Merge both agents' findings into one list, grouped by file, ordered by severity:

Each finding needs a location and a concrete fix, not just a complaint.

End with an explicit verdict: Approve (no CRITICAL or HIGH), Warning (HIGH only), or Block (any CRITICAL). If any secret may have been exposed, say so first and recommend rotating it.