theolegr/harness-template
A harness for coding agents, installed in one command: goal, backlog, boot sequence, checks, guard hooks, reviewer and strategist subagents. Claude interviews you to fill it in; /ship builds one item at a time with an independent review; --
stack: Python
ARCHETYPE
Automator
Hooks on every lifecycle event: format, lint, notify, log.
GUARDRAILS
3/5
Blocks destructive commands · Pre-tool screening hook · No YOLO mode · details
Quality 23/100 Guardrails v2
Copy this rig
# review before running: this installs third-party code
$ npx degit theolegr/harness-template/project/.claude ./rig-harness-template # inspect, then merge into .claude/ MCP servers are added to Claude Code at local scope; env vars are shown as YOUR_… placeholders — we never store values. Files are fetched with degit into a separate folder so you can review before merging.
$ npx degit theolegr/harness-template/project/.claude/skills/design .claude/skills/design $ npx degit theolegr/harness-template/project/.claude/skills/harness-init .claude/skills/harness-init $ npx degit theolegr/harness-template/project/.claude/skills/ship .claude/skills/ship
$ curl -fsSL --create-dirs -o .claude/agents/reviewer.md https://raw.githubusercontent.com/theolegr/harness-template/main/project/.claude/agents/reviewer.md $ curl -fsSL --create-dirs -o .claude/agents/strategist.md https://raw.githubusercontent.com/theolegr/harness-template/main/project/.claude/agents/strategist.md
Merge into .claude/settings.json (project) or ~/.claude/settings.json (user). Hook commands reference scripts in the source repo — copy those too.
{
"hooks": {
"PreToolUse": [
{
"matcher": "Bash",
"hooks": [
{
"type": "command",
"command": "python3 \"$CLAUDE_PROJECT_DIR/harness/scripts/hooks/guard-bash.py\""
}
]
}
]
}
} Skills (3)
Subagents (2)
| reviewer model: opus | Independent reviewer (the "checker" of the maker/checker split). Reviews a diff against a backlog item's acceptance criterion and returns a PASS/FAIL verdict, plus non-blocking findings (bugs, tech de |
| strategist model: opus | Product strategist and brainstorm partner. Surveys the whole project (goal, state, backlog, history, code, decisions), answers questions about it, and proposes where it should go next — new features, |
Hooks (6)
| event | matcher | runs |
|---|---|---|
| SessionStart | * | cd "$CLAUDE_PROJECT_DIR" && ./harness/scripts/link-skills.sh 2>&1; ./harness/scripts/harness-status.sh 2>&1 | head -60 |
| SessionStart | * | python3 "$CLAUDE_PROJECT_DIR/harness/scripts/hooks/other-sessions.py" |
| PreToolUse | Bash | python3 "$CLAUDE_PROJECT_DIR/harness/scripts/hooks/guard-bash.py" |
| Stop | * | [ -f "$CLAUDE_PROJECT_DIR/harness/dashboard.html" ] && python3 "$CLAUDE_PROJECT_DIR/harness/scripts/dashboard.py" >/dev/null 2>&1; exit 0 |
| Stop | * | bash "$CLAUDE_PROJECT_DIR/harness/scripts/hooks/stop-check.sh" |
| SessionEnd | * | python3 "$CLAUDE_PROJECT_DIR/harness/scripts/hooks/other-sessions.py" end |
Permissions
deny (0)
—
ask (0)
—
allow (13)
Bash(./harness/scripts/harness-check.sh)
Bash(./harness/scripts/harness-status.sh)
Bash(./harness/scripts/feature.sh *)
Bash(./harness/scripts/link-skills.sh)
Bash(./harness/scripts/state.py)
Bash(./harness/scripts/dashboard.py *)
Bash(./harness/scripts/disk.py)
Bash(git status *)
Bash(git diff *)
Bash(git log *)
Bash(git show *)
Bash(git add *)
Bash(git commit *)
Similar rigs
victorkzam/claude-code-setup
My daily-driver Claude Code setup: design→build→ship agentic workflow, model-routing rules, counter-model review, and fail-closed hooks. A sanitized, clone-and-use export.
Orchestrator 845 tok · · Q0
Altafhossain72/claude-ship-pipeline
/ship: a 5-agent Claude Code pipeline (planner, coder, tester, reviewer, documenter) that ends with a reviewed local commit on a feature branch
Orchestrator 349 tok · · Q0
Adityaraj0421/naksha-studio
A virtual design team for Claude Code, Cursor, Windsurf, Gemini CLI, and Copilot — 26 roles, 62 commands, 15,000+ lines of expert design knowledge. Your agency's design brain, inside your terminal.
Minimalist 2.4k tok · · Q3
mblua/AgentsCommander
Stop letting your experience disappear between sessions. Build your own coding-agent ecosystem: keep roles, skills, and lessons in files you can review, refine, and reuse. Start with one agent or coordinate teams in real terminals. Open sou
Minimalist 40 tok · · Q15