Skip to content
All skillsQuality

Check skill

Review Before Commit

draft, under review3 phases1 bundled files

The review I would give the diff before it goes in: smallest change that works, no new deps or patterns for no reason, no any on real data, no dead code, logic on the right side of the server boundary.

Install
/plugin marketplace add Selwynuy/selwynuy
/plugin install selwyn-handbook@selwyn-handbook
# then run: /selwyn-handbook:review-before-commit

Or read it as SKILL.md.

When it activates

Use this skill when after writing or changing code, before committing it.

The workflow

  1. Diff

    Read the actual diff (git diff), not the intent. Confirm the change is the smallest edit that solves the problem and did not rewrite or reformat code it did not need to touch.

    working-with-me

  2. Standards

    Check against the standing rules: no new dependency or pattern without a clear reason, no any for non-trivial data, no dead code or leftover console logs, no business logic pushed into client components, secure-by-default wiring kept intact.

    working-with-mesystem-architecturetype-system

  3. Report

    List what must change before commit and what is optional, plainly. Do not commit on the author's behalf; the review ends at a clear verdict, the human decides.

    security-by-design

What ships in the bundle

  • referencereferences/review-checklist.mdThe standards a diff is held to, grouped by scope, correctness, types, and architecture, each with what a violation looks like.

0 run, the rest load on demand.