Individual skill

factory-verify

Verify an open factory PR before human review - re-runs gates, checks the test proves the fix, checks scope and test tampering. Use when reviewing a factory PR, running the PR review routine, or asked to independently check a change.

template/.claude/skills/factory-verify/SKILL.md

Read pinned source

Source commit 8af116567166a0a16588b7ab1b9934ece0b775bc

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Instructions only
Last checked
Nov 5, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
328
Repository last updated
Aug 21, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Factory verify

Use this when a PR already exists and you are the check standing between it and a human.
For verification during implementation, the `factory-verifier` subagent is the right tool;
this skill is the PR-level version and can be driven by a GitHub-triggered routine.

## Procedure

1. Read `docs/factory/CONTRACT.md`, then `docs/factory/CHARTER.md` for the tier,
   load-bearing globs, and definition of done.
2. Check out the PR branch.
3. Run the required gate level yourself. Do not trust the `FACTORY_GATES` line in the PR
   body; produce your own and compare. A mismatch is the finding.
4. Run the checks the deterministic gates cannot make: