skeeper

What problem does it solve?

Skeeper keeps specification artifacts (like SPEC.md, ADRs, RFCs, and other plan/PRD/TechSpec markdown) versioned and synchronized alongside code without cluttering the main repository’s PR diffs.

Core Features & Use Cases

• Lockfile-pinned, sidecar-backed spec history: skeeper.lock records exactly which sidecar commits correspond to each main commit, so you can prove what spec state shipped.
• Strict managed Git workflows: Git hooks mirror staged content into a sidecar repo, then update and stage skeeper.lock before your main commit proceeds.
• Safe, auditable bypasses: Use SKEEPER_SKIP to bypass once with an audited record, then rely on status and repair to recover.
• Namespace support for shared sidecars: Multiple projects can share one sidecar remote using branch-aware refs under a namespace.
• Common recovery & CI readiness: status --check is CI-friendly, while repair diagnoses and safely repairs drift, hook state issues, and interrupted transactions.

Quick Start

Run skeeper init in your repo, track your spec files with --track globs, commit .skeeper.yml, and let the managed hooks sync updates into the sidecar with a pinned skeeper.lock.