Lean body (~30 lines) with no padding or explanation of concepts Claude already knows; every line in the Workflow and Quality gate earns its place, matching the lean-and-efficient anchor.

As an instruction-only skill it gives concrete, specific guidance — named files (AGENTS.md, CLAUDE.md, PR template), specific comment categories to audit, and named checks to record — so code absence is not penalized per the scoring notes.

A clear five-step sequence with an explicit verification step (run build/tests, record exact commands and outcomes, state checks not run) plus a quality-gate checklist that verifies claims against the diff and command output.

Under 50 lines with no need for external references, organized into well-labeled Workflow and Quality gate sections, qualifying for the top anchor under the simple-skills note.

Lists multiple concrete actions — "final diff audit, documentation check, verification record, or pull request description" — rather than vague language, matching the multiple-specific-actions anchor.

Explicitly answers both what (the audit/check/record/PR-description actions) and when ("Use when a non-trivial code change is substantially complete"), with an explicit Use-when trigger clause.

Covers natural terms users would say ("pull request", "diff", "documentation", "code change", "verification"), fitting the good-coverage anchor; the gating phrasing is slightly internal but the action terms are natural.

Targets a clear niche — finishing a substantially-complete change into reviewer-facing delivery — with distinct triggers unlikely to fire for general coding skills.