compozy

compozy / skeeper

Public

Version your spec artifacts — PRDs, tech specs, ADRs, AI plans — in a sidecar Git repository, without polluting your main PRs.

45
2
100% credibility
Found May 08, 2026 at 45 stars -- GitGems finds repos before they trend. Get early access to the next one.
Sign Up Free
AI Analysis
Go
AI Summary

Skeeper keeps design documents and specs in a separate version-controlled storage while pinning exact versions with a tiny lockfile in the main project to prevent drift.

How It Works

1
🔍 Discover cleaner code reviews

You notice specs and design notes clutter every pull request, making code reviews harder.

2
📥 Get the tool

Download the simple helper that keeps notes safe without messing up your code changes.

3
⚙️ Set it up once

Run a quick setup to connect a private storage spot just for your project notes.

4
✏️ Write notes next to code

Add your SPEC notes or plans right where the code lives, naturally and organized.

5
✅ Save changes together

Commit your code and notes — the helper quietly saves notes securely in their spot.

6
🚀 Share clean updates

Push your changes; everything checks out perfect, with notes safe and ready anytime.

🎉 Perfect reviews every time

Your team reviews just the code changes, while notes stay fully tracked and easy to revisit.

Sign up to see the full architecture

5 more

Sign Up Free

Star Growth

See how this repo grew from 45 to 45 stars Sign Up Free
Repurpose This Repo

Repurpose is a Pro feature

Generate ready-to-use prompts for X threads, LinkedIn posts, blog posts, YouTube scripts, and more -- with full repo context baked in.

Unlock Repurpose
AI-Generated Review

What is skeeper?

Skeeper lets you version spec artifacts like PRDs, tech specs, ADRs, and AI plans in a dedicated sidecar Git repository, keeping your main repo's PRs code-only via a tiny `skeeper.lock` file that pins exact sidecar commits. Built in Go, it uses managed Git hooks to sync files automatically on commit and push, with CLI commands like `hydrate`, `sync`, `verify`, and `reconcile` for recovery and diffs. A GitHub Action handles CI verification, supporting github version management and version github actions workflows.

Why is it gaining traction?

Unlike dumping docs into main branches—which bloats diffs—or letting specs drift, skeeper enforces github version control unity with strict hooks that fail commits on sync issues, plus branch-aware sidecar branches for full git blame and history. Namespaces avoid collisions in shared repos, and agent-friendly JSON output pairs well with version github copilot for AI-generated plans. The lockfile's digest and byte counts add reliability without complexity.

Who should use this?

Engineering teams generating SPEC.md files via AI agents, orgs maintaining ADRs or RFCs without PR noise, or solo devs tracking spec evolution alongside code. Ideal for projects where reviewers focus on implementation, not docs, and you need github version tags or badges for releases.

Verdict

Worth trying for spec-heavy workflows—solid CLI, docs, and tests despite 45 stars and 1.0% credibility score signaling early maturity. Install via `go install` and `skeeper init`; pair with version github actions for polish, but expect tweaks as it grows.

(198 words)

Sign up to read the full AI review Sign Up Free

Similar repos coming soon.