Review behavior, risk and validation in code changes and provide evidence-based feedback.
Prepare a structured review of a set of code changes: what was implemented, which requirements it addresses, the commit range to inspect, and the main risks in completeness, correctness, structure and testing. Use it before merging a feature, checking a fix or reviewing a substantial stage of work.
Provide the requirements, commits or diff and your known concerns. The skill helps organize the review, rank findings and suggestions by importance, and identify the relevant code locations and supporting evidence. Results also state what was outside the review and what still needs verification, helping you decide which fixes and tests come next and when integration can proceed.
Examples describe the request and the shape of the expected deliverable; they are not completed run results.
Open a read-only review of a3f9c21..e81b0d4 against these three acceptance criteria; list what you considered but won't judge this round before the verdict.
A review report: scope statement, itemized findings and the tradeoffs needing your call — code and branch state untouched.
Nine review comments came back: triage each into fix / needs-evidence / decline-with-reason — suggestions are not commands.
A per-comment disposition table with its basis; edit scope stays governed by the task's authorization.
iOS · Android
iOS
Android
MIT
MIT (root LICENSE)
The pinned skill subtree and shipped references were audited; full applicable license and per-file adaptation/asset notes are preserved under references/licenses/ and references/PROVENANCE.md.
Publication commit 25e07dbeeb, audited source 84c524b6fb; catalog digest iOS 46196ba57ed7… · Android 16de89d019e2….
Version records ship with the signed catalog; the target and released versions are shown below.
