Skip to content

ericrisco/rsc-harness / skills/harness

harness

Flagged

Use when governing a workspace's control plane, code or not — the `01-TOOLS/` tooling layer, the `02-DOCS/` chaos→knowledge wiki, the root Knowledge map. Audits it, migrates legacy `XX-*` folders, scaffolds provider tooling, sweeps the inbox, eats a file the person hands over ("cómete este fichero", "guárdalo en la documentación": moved into 02-DOCS/raw/ and documented), writes root CLAUDE.md/AGENTS.md. NOT the bootstrap front door (that is `init`, which hands off here).

references/agents-md-template.md

View on GitHub
# AGENTS.md — {{PROJECT_NAME}}

> Template generated by `harness` on {{TODAY}}.
> For agents OTHER than Claude Code (Codex, Cursor, Aider, etc.), this
> file is the first read. For Claude Code, see `CLAUDE.md` (both files
> are aligned, but `CLAUDE.md` may have Claude-specific runtime details).

## Workspace

Multi-repo orchestrated at the root level. Each subproject is an
independent Git repo. The root is NOT a repo.

## Quick map

| Path | Role |
|------|------|
{{SUBPROJECT_ROWS}}
| `01-TOOLS/` | Operational tooling per external provider. |
| `02-DOCS/` | LLM wiki (`raw/` + `wiki/` + `index.md` + `log.md`). |

## Minimum rules

1. **Before editing a subproject**: `git -C <subproject> status --short`.
2. **Do not commit without asking**.
3. **Do not touch `01-TOOLS/**/.env`**. These are real credentials.
4. **Do not touch generated outputs**: `node_modules/`, `.venv/`,
   `.next/`, `__pycache__/`, `.dart_tool/`, `build/`.
5. **To add a new external tool**, use `01-TOOLS/_TEMPLATE/`.
6. **For reusable documentation**, write to `02-DOCS/raw/<topic>/` and
   compile in `02-DOCS/wiki/<topic>/`. The protocol lives in
   `harness/references/wiki-protocol.md` (embedded in the
   skill).

## Per-subproject commands

{{SUBPROJECT_COMMANDS}}

## Differences from `CLAUDE.md`

If there are any, they're documented here. By default both files cover
the same rules.
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall