library-diff-reviewer

Reviewing a skill-library pull request for registration consistency involves verifying catalog placement, README status text, decision-log entries, and count arithmetic across the library to ensure additions are correctly registered and ready to merge.

Collision detection in a skill-library pull request compares added or modified skills against the shipped corpus and against other skills in the same PR to catch ambiguous overlaps and ensure coherence before merging.

Validating retired skills in a pull request confirms retired skills are recorded properly, references are cleaned up, and deprecation steps match the existing retirement plan before the changes are merged.

Checking library-wide diff coherence requires fresh validator evidence, catalog and README reconciliation, in-batch sibling collision checks, and composed per-skill quality review to produce a final approve or request-changes verdict.

Fresh validator evidence is required to review a skill-library pull request end to end, ensuring registration consistency, collision safety, and diff coherence are validated before the final merge verdict is issued.

Reviewing multiple skill additions in the same pull request for collision safety involves in-batch sibling collision checks that compare added or modified skills against each other and the shipped corpus to catch ambiguous overlaps.