repo-church

Repo Church Agent Skills

Repo Church is an agent-agnostic skill package for Bible-grounded repository planning, phase chaining, gap closure, and collaborative verification.

It helps agents and humans turn a durable Repo Bible into executable work: first clarify the product doctrine, then validate assumptions, plan phases, hand off execution, verify outcomes, and refresh the source of truth.

Start Here

If you are new to Repo Church, follow the docs in this order:

1. Docs Index - the full learning path and reference map.
2. Getting Started - install the package and run the first workflow.
3. Concepts - learn the Bible, lifecycle, gates, ledgers, and signoff model.
4. Lifecycle - see how the staged loop works from intake to refresh.

The README is intentionally short. The detailed command, skill, agent, CLI, validation, and reference docs live under docs/.

Install

Package source repo: If you are working inside a clone of this repository, do not run npx skills add . --all from the package root—it replaces skills/ with symlinks into .agents/skills/. Refresh global installs from outside the repo: npx skills add chendrizzy/repo-church --all -g.

Global install from GitHub (skills.sh leaderboard uses install telemetry from this path):

npx skills add chendrizzy/repo-church --all -g

Equivalent full URL:

npx skills add https://github.com/chendrizzy/repo-church --all -g

From a parent checkout that contains this package:

npx skills add ./agent-skills/repo-church --all

From this package root:

npx skills add . --all

Install only the core lifecycle skill:

npx skills add . --skill church

Install the Bible generator and lifecycle router together:

npx skills add . --skill repo-bible --skill church

First Run

Use church:gather when you want the framework to inspect a project and choose the next gate. Under the hood, the command starts with deterministic context loading:

skills/church/scripts/church init --root <repo> --mode brownfield --project-name "<name>"
skills/church/scripts/church context load --root <repo> --format markdown --include-history
skills/church/scripts/church bible inventory --root <repo> --format markdown
skills/church/scripts/church moat check --root <repo> --allow-incomplete --format json

For a small low-risk task, use church:quick-rite. For anything that changes strategy, architecture, security, UX, phase scope, or Bible doctrine, use the staged lifecycle.

Core Loop

church:gather
  -> church:discern
  -> church:canonize
  -> church:commission
  -> church:fellowship
  -> church:bless
  -> church:renew
  -> repeat

Stage	Purpose
church:gather	Load context, initialize state, inventory Bible artifacts, define or check the moat, and choose the next route.
church:discern	Harden assumptions, source claims, and close ambiguity before planning.
church:canonize	Create or review anchors and specs with requirement traceability.
church:commission	Freeze scope, split safe workstreams, and prepare execution handoff.
church:fellowship	Review, run UAT, and record mutual signoff where needed.
church:bless	Gate merge or release readiness against evidence, rollback, and Bible alignment.
church:renew	Refresh the Bible, capture learnings, and set up the next cycle.

See Lifecycle and Commands for the complete operator path.

Why It Works

Repo Church is useful when ordinary agent planning is too easy to drift, overfit to stale context, or skip verification. It makes the work harder to fake by requiring:

• a durable Repo Bible as the strategic source of truth,
• CLI-first inventory and validation before broad synthesis,
• confidence labels for assumptions and claims,
• phase anchors that trace to requirements and doctrine,
• gap ledgers with owners and closure proof,
• execution handoffs with validation and rollback,
• collaborative UAT for subjective or high-risk work,
• refresh loops when implementation changes doctrine.

The goal is not ceremony. The goal is to make the next agent or human able to continue without re-deriving the project.

Documentation

Use docs/INDEX.md as the documentation home.

Key pages:

• Getting Started
• Concepts
• Lifecycle
• Commands
• CLI and Tooling
• Skills
• Agents
• Package Authoring
• Reference Index

Validate

From this package root: