Agent skill · personamanagmentlayer
code-review-workflow
Review a change in a fixed order — context, correctness, security, then style — and write feedback that is actionable and ranked by severity. Use when the user asks for a code review, wants a pull request or diff reviewed before merge, asks whether a change is safe to ship, or when the task involves reviewing a patch, giving review feedback, triaging review comments, or setting review standards for a team.
What it needs
About 5k tokens when loaded.
What this skill does
Code Review Workflow The procedure for reviewing a change. For the body of knowledge behind the judgements — what good code looks like per dimension — use the code-review-expert skill; this skill is the order of operations and the shape of the output. When to Use This Skill The user asks to review a pull request, a diff or a patch A change needs assessment before merge or deploy The user asks "is this safe to ship?" Review feedback needs triaging or prioritising A team wants a review standard defined Core Concepts Order Matters Reviewing in a fixed order prevents the common failure: spending the whole review on naming and never reaching the concurrency bug. Correctness and security are examined while attention is fresh; style comes last because it is the cheapest to fix and the easiest to automate away. Severity, Not Volume Twelve comments of equal weight leave the author guessing. Every comment carries a severity, and a review with no blocking comments says so explicitly. Severity Meaning Merge ------------- ----------------------------------------- ---------------------- Blocking Incorrect, unsafe, or loses data No Important Should change, but not a correctness risk Author's call, argued Minor Improvement, preference with a reason Optional Question Reviewer does not understand yet Answer, may reclassify A Finding Needs a Failure An assertion that something is wrong must come with the input, state or sequence that makes it wrong. "This could race" is an opinion; "two requests for the same order both pass the check at line 41 and both insert" is a finding. Review the Change, Not the Codebase Pre-existing problems the diff merely touches are not this author's to fix. Note them separately, as a follow-up, not as a merge condition. The Workflow 1. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills personamanagmentlayer/code-review-workflow