Skip to content

v0.1.0 — initial public release

Choose a tag to compare

@coolsocket coolsocket released this 22 Jun 14:10

RePERS v0.1.0 — initial public release

First public release of the RePERS harness. Reusable Planning,
Execution, Review, and Release — a local-first agent workflow
operating layer.

What's in the box

  • .repers/ runtime — stdlib-only Python CLI (repers.py) with subcommands for preflight, planning, dispatch, review, packaging, hooks, and a full local verification gate.
  • 24-entry capability registry — canonical inventory of reusable workflows, scripts, hooks, gates. Queryable via repers.py capabilities.
  • 4 Codex skillsrepers-init, repers-bug-hunt, repers-release-pack, repers-sinkin.
  • Deterministic orchestration fixturefixture --action prove validates conflict-safe worker dispatch + join/review WITHOUT a real agent backend.
  • Installable Git pre-commit hook — warn (default) or strict mode.
  • Transferable release packrepers-release-pack.zip (install archive + readiness + handoff + remote bootstrap + benchmark + state + continuation, all checksum-verifiable).
  • JSON evidence for every gate — pipe to jq, store in CI, audit later.

Quickstart

# As a Codex plugin:
/plugin marketplace add coolsocket/repers
/plugin install repers
/repers-init

# OR as a repo-local runtime:
git clone https://github.com/coolsocket/repers.git
python repers/.repers/scripts/repers.py install --target /path/to/your-repo --json

See the README for the daily
workflow and the FAQ.

Assets

Asset Purpose
repers-0.1.0.zip Installable runtime archive (extract → run install_repers.py)
repers-release-pack.zip Transferable bundle for another repo to verify end-to-end
repers-verify-all.json Full local-gate evidence (328 KB)
repers-release-evidence.json Publish-readiness report (package + registry + governance + Git state)

What's next

See ROADMAP.md
next milestones include richer DAG planning artifacts, branch/PR automation,
and (later) optional CodeGraph + signed artifacts.

Contributions welcome — start with CONTRIBUTING.md
and please run preflight --query "<your-intent>" before proposing new
capabilities.