From 6bc1f7cc1040de984d8530e86783a5cbe237c8d6 Mon Sep 17 00:00:00 2001 From: jochen Date: Tue, 3 Nov 2026 01:45:29 +0100 Subject: [PATCH] research-reader cites no path, as playbook 01 asks; AGENTS.md rewrapped --- .claude/agents/research-reader.md | 6 +++--- AGENTS.md | 5 +++-- 2 files changed, 6 insertions(+), 5 deletions(-) diff --git a/.claude/agents/research-reader.md b/.claude/agents/research-reader.md index 128874a1..bbf299db 100644 --- a/.claude/agents/research-reader.md +++ b/.claude/agents/research-reader.md @@ -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:`, `git grep 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/`, 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), diff --git a/AGENTS.md b/AGENTS.md index 3083ebb5..c4c4d7a0 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -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