Two files, one repository
hoangnb24/repository-harness ships 2 formats across 2 indexed files. The question worth asking is whether the second one says anything the first does not.
CompareAGENTS.md ↔ CLAUDE.md
| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 1 | 1 | 1 | 33% |
| Commands | 0 | 0 | 0 | — |
| Section tags | 1 | 1 | 0 | 50% |
What each file covers
Sections
1 shared · 1 only in A · 1 only in B- − Agent Instructions
- + Project Rules
- Harness
Commands
neither file has anySection tags
1 shared · 1 only in A · 0 only in B- − agent-behaviour
- do-not
Line diff
hoangnb24/repository-harness · AGENTS.md
@@ −1 @@
1# Agent Instructions
2
3<!-- HARNESS:BEGIN -->
4## Harness
5
6Start with the requested outcome and use the repository as the system of record.
7Read `docs/WORKFLOW.md` and only relevant product, design, plan, code, and
8validation material.
9
10- Answers, explanations, reviews, diagnoses, plans, and status reports are
11 read-only. Inspect only what is needed; change nothing.
12- For a bounded change, inspect affected behavior and proof, implement, and
13 validate. No control-plane operation is required.
14- Use one `docs/plans/active/` file when work spans sessions, coordinates
15 contributors, has dependencies, or needs recovery. Move it to
16 `docs/plans/completed/` only after validation.
17- Before editing, identify repository authority for each new externally
18 observable policy. If materially different choices remain open, stop before
19 edits; configurable defaults are not authority.
20- For architecture, reliability, security, or quality invariant work, read
21 `docs/patterns/encoding-invariants.md` and enforce only accepted rules.
22- Report reusable agent friction. Change guidance, tools, runbooks, or validation
23 for that purpose only when explicitly asked to use `$improve-harness`.
24- Also pause when product intent remains ambiguous, recovery is difficult,
25 validation is weakened, or authority is insufficient.
26- Claim completion only with executable or observable evidence. Report outcome,
27 changes, validation, and unresolved risks.
28
29Harness has no task database or orchestration lifecycle. Use repository plans
30and behavior-level proof; do not create parallel control-plane state.
31<!-- HARNESS:END -->
32
hoangnb24/repository-harness · CLAUDE.md
@@ +1 @@
1# Project Rules
2
3<!-- HARNESS:BEGIN -->
4## Harness
5
6Claude Code does not auto-load `AGENTS.md`. Import that single canonical
7project instruction source. Keep this bare `@` line outside backticks so the
8import remains active.
9
10@AGENTS.md
11<!-- HARNESS:END -->
12
@@ −1 +1 @@
1−# Agent Instructions
1+# Project Rules
22
33 <!-- HARNESS:BEGIN -->
44 ## Harness
55
6−Start with the requested outcome and use the repository as the system of record.
7−Read `docs/WORKFLOW.md` and only relevant product, design, plan, code, and
8−validation material.
6+Claude Code does not auto-load `AGENTS.md`. Import that single canonical
7+project instruction source. Keep this bare `@` line outside backticks so the
8+import remains active.
99
10−- Answers, explanations, reviews, diagnoses, plans, and status reports are
11− read-only. Inspect only what is needed; change nothing.
12−- For a bounded change, inspect affected behavior and proof, implement, and
13− validate. No control-plane operation is required.
14−- Use one `docs/plans/active/` file when work spans sessions, coordinates
15− contributors, has dependencies, or needs recovery. Move it to
16− `docs/plans/completed/` only after validation.
17−- Before editing, identify repository authority for each new externally
18− observable policy. If materially different choices remain open, stop before
19− edits; configurable defaults are not authority.
20−- For architecture, reliability, security, or quality invariant work, read
21− `docs/patterns/encoding-invariants.md` and enforce only accepted rules.
22−- Report reusable agent friction. Change guidance, tools, runbooks, or validation
23− for that purpose only when explicitly asked to use `$improve-harness`.
24−- Also pause when product intent remains ambiguous, recovery is difficult,
25− validation is weakened, or authority is insufficient.
26−- Claim completion only with executable or observable evidence. Report outcome,
27− changes, validation, and unresolved risks.
28−
29−Harness has no task database or orchestration lifecycle. Use repository plans
30−and behavior-level proof; do not create parallel control-plane state.
10+@AGENTS.md
3111 <!-- HARNESS:END -->
3212
