Design and stage repository pre-commit checks that preserve partial staging, meet a latency budget, mirror mandatory CI controls, and recover cleanly when setup fails.
A pre-commit hook can look correct while quietly doing the wrong job. It can format an unstaged hunk, turn a five-second commit into a two-minute wait, depend on a runtime that half the team cannot bootstrap, or become the only place a security check runs. A failed installer can leave the lockfile, hook path, dependencies, and staged index in an ambiguous state.
Pre-commit Rollout treats the hook as one control in a delivery system. It inventories the real repository, Git hook resolution, package-manager artifacts, worktree and staged state, supported environments, command sources, CI authority, and mutation permissions before proposing a framework. It separates fast staged-file feedback from full checks that belong in pre-push or CI, preserves partially staged work, measures each command separately, and keeps mandatory controls authoritative after a local bypass.
The workflow covers native hooks, pre-commit, Husky, lint-staged, and Lefthook. It defines observed, designed, shadow, blocking, verified, and rolled-back states; a control-placement matrix; fixture-based verification; bypass governance; partial-install recovery; rollback triggers; and a handoff that keeps missing evidence visible. It does not install packages, edit a repository, alter Git configuration, stage files, commit, bypass a hook, or change CI unless that authority is explicitly granted.
Version 1.0.0 was reviewed on 2026-07-24 and evaluated through Codex CLI with gpt-5.6-sol in 12 fresh read-only contexts. The candidate scored 100 across three cases, compared with 74.17 for the same agent without the skill and 70 for the exact free upstream. It passed all three cases and led the upstream by 30 points overall. The evaluation covers the supplied cases; it does not prove a real repository, hook installation, supported platform, latency target, CI rule, or rollout state.
The reviewed package SHA-256 is 0eac62e8f697b2cbf108cc030e455392c6e715680720e6c83f351850a9ab657d. Maintenance and install support are handled by the platform-operated publisher for this listing.
Input
The repository has partially staged TypeScript, unstaged Python, pnpm and Ruff tooling, a user-level hooks path, three supported operating systems, and a ten-second warm target. Design authority is granted but mutation authority is not.
Output
A read-only evidence ledger, staged-file control map, framework and hook-path decision, measured placement of fast checks versus pre-push or CI, shadow-to-blocking gates, partial-stage fixtures, blockers, and a designed verdict.
Input
A package-manager install timed out after changing the manifest, lockfile, hook directory, and dependency store. A process may still run, the pre-mutation hashes are incomplete, and the requester cannot stop, delete, install, stage, commit, bypass, or push.
Provide the repository and worktree, current HEAD and staged or unstaged state, package-manager and runtime files, existing hook and CI configuration, exact command timings, supported developer environments, recent bypasses or incidents, latency target, mandatory controls, and separate read, install, edit, stage, commit, bypass, CI, and branch-policy authority. Ask to design, stage, diagnose, recover, verify, or hand off a pre-commit rollout. The skill keeps unobserved state and unauthorized mutations explicit.
Repository root, HEAD and branch, worktrees, current staged, unstaged, partially staged, and untracked state, existing hooks, Git hook-path configuration, manifests, lockfiles, runtime selectors, and contributor instructions.
Exact formatter, linter, typecheck, test, secret-scan, and policy command sources; individual cold or warm timings; current CI or server counterparts; and the accepted commit-latency budget.
Supported operating systems, shells, runtimes, package-manager bootstrap constraints, team or pilot cohort, existing adoption and bypass behavior, and recent incidents.
Separate permission to read, install, edit, change Git configuration, stage, commit, bypass, change CI or branch policy, approve blocking rollout, roll back, and declare verification.
SKILL.md; pre-commit control-placement matrix; rollout, failure-isolation, recovery, rollback, and handoff reference
No reviews yet.
Output
An evidence hold, read-only process and filesystem reconciliation sequence, ambiguous-state branches, protected user work, prohibited actions, recovery verification, a blocked verdict, and one safe next action.
Input
A Yarn 4 service has slow whole-tree checks, merge-blocking CI, recent local bypasses, and a credential incident. Security wants staged secret and formatting checks under five seconds with no automatic changes.
Output
An exact artifact and timing ledger, staged read-only control design, platform and bootstrap decision, representative shadow cohort, pass and failure fixtures, CI parity, recorded emergency bypass, rollback policy, acceptance gates, and an owner-approved next action.
Creator
Ddolven
