novox/hq
18
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

research-reader cites no path, as playbook 01 asks; AGENTS.md rewrapped
mesh/delivery merged: source.main moved to novox/hq@92fa66f4e79f
Details
mesh/check pass 6bc1f7cc1040 on f6bd4246b0d7 | carried from 979bf3f19cce | unit 39 run, 0 kept, 1 skipped | integration 39 run, 0 kept, 1 skipped | co…

Browse Source
This commit is contained in:
jschoubben
2026-11-03 01:45:29 +01:00
parent 1a389be090
commit 6bc1f7cc10
2 changed files with 6 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.claude/agents/research-reader.md
+3 -3
View File
@@ -15,13 +15,13 @@ Read first: the questions you were given, the effort's sections the caller names
How you read:
- **Code on main only, never a working copy's checkout.** Other sessions work in the local clones under the
projects folder; never check out, reset, stash, pull or commit there. Run `git fetch origin` in the
- **Code on main only, never a working copy's checkout.** Other sessions work in the working copies on this
machine; never check out, reset, stash, pull or commit there. Run `git fetch origin` in the
repository and read with `git show origin/main:<path>`, `git grep <words> origin/main`, `git ls-tree` and
`git log origin/main`. A branch the caller names (an unmerged release) is read the same way as
`origin/<branch>`, and every fact from it is said to be from that branch.
- **Each fact with its source:** the repository, the short commit of `origin/main` you read, and the function
or type (a manifest field by its name). Never a line number alone.
or type (a manifest field by its name); never a path or a line number.
- **Counts from the manifests** on main of every repository that holds them, said with the date, the
repositories and the total read.
- **A try in process** (a local NATS server on the loopback, a Go test program in a temporary directory),
AGENTS.md
+3 -2
View File
@@ -14,8 +14,9 @@ through them. Thin skills in `.claude/skills/` wrap these playbooks for invocati
authoritative and adds only the mechanical scaffolding. Four reviewer agents in `.claude/agents/` carry
playbook 01's *Review by architectural domain*, two architectural domains each:
`review-security-and-upgrade`, `review-seams-and-tools`, `review-running-and-testing` and
`review-health-and-events`; the lead starts all four side by side and rules on their findings. A fifth, `research-reader`,
carries one reading task of playbook 01's step 5: code on main, counts from the manifests, a try in process.
`review-health-and-events`; the lead starts all four side by side and rules on their findings. A fifth,
`research-reader`, carries one reading task of playbook 01's step 5: code on main, counts from the manifests, a
try in process.
## The development cycle