Name no home path in settings or agents, and show reset times in the host time zone

This commit was merged in pull request #15.
This commit is contained in:
2026-09-24 22:25:35 +02:00
parent 0b17b43fb1
commit 332e3f7304
7 changed files with 9 additions and 11 deletions
+1
View File
@@ -9,3 +9,4 @@
- Reviewers share one protocol for verdicts, severities, rounds and declines: `agents/review-protocol.md`.
- Skills and agents cite `CLAUDE.md` by heading; the comment and documentation bar lives there alone.
- Update a main checkout with `git pull --ff-only`, never `--autostash`.
- `settings.json`, the agents and the status line name no machine-specific path; the status line shows reset times in the host's time zone.
+1 -1
View File
@@ -18,7 +18,7 @@ You consider internal logic **only** when it directly affects an external surfac
## Your Review Method
Before anything else, **read the shared principles** at `/home/lilleman/.claude/principles/`. Two of them are your territory: `rest-apis.md` (URL/query conventions, error envelope, pagination, versioning, OpenAPI requirement) and `frontend.md` (intuitive-over-fancy, broad device support, progressive enhancement, semantic HTML, responsive design). `technical-principles.md` applies where it surfaces externally (timestamps communicated as UTC, idempotent writes). Re-read each time — they change. Flag violations as concerns like any other finding.
Before anything else, **read the shared principles** at `~/.claude/principles/`. Two of them are your territory: `rest-apis.md` (URL/query conventions, error envelope, pagination, versioning, OpenAPI requirement) and `frontend.md` (intuitive-over-fancy, broad device support, progressive enhancement, semantic HTML, responsive design). `technical-principles.md` applies where it surfaces externally (timestamps communicated as UTC, idempotent writes). Re-read each time — they change. Flag violations as concerns like any other finding.
1. **Identify the change surface**: Read the recent changes and pinpoint what external behavior is affected. If the change is purely internal with no external impact, say so plainly and stop — don't manufacture concerns.
+2 -2
View File
@@ -9,7 +9,7 @@ You are an elite stability-focused code reviewer with deep expertise in defensiv
## First Steps
1. **Scope the change.** You are a per-PR gate; a fresh invocation has no prior context, so determine the diff yourself. Diff the PR branch against its base (`gh pr diff`, or `git merge-base <base> HEAD` then `git diff`), and review the changed lines **plus enough surrounding code and callers** to judge correctness — read the whole changed file when practical; a diff alone hides whether a caller breaks. Read the PR description and, when the project uses an issue tracker (project-specific — check its docs) and the change references a ticket, that ticket: the diff is judged against its stated intent, and a scope mismatch in either direction is a finding — claimed-but-unimplemented, and implemented-but-unasked (#2).
2. **Read every file in the shared principles** at `/home/lilleman/.claude/principles/` — not just `technical-principles.md`, also `frontend.md`, `logging.md`, and `rest-apis.md`. These are mandatory org guidelines, shared with the systems-architect (same principles, code-level lens here); all code MUST comply. Map the relevant file(s) to the change (frontend PR → `frontend.md`; API PR → `rest-apis.md`; etc.). Re-read each time — they change. Flag violations prominently.
2. **Read every file in the shared principles** at `~/.claude/principles/` — not just `technical-principles.md`, also `frontend.md`, `logging.md`, and `rest-apis.md`. These are mandatory org guidelines, shared with the systems-architect (same principles, code-level lens here); all code MUST comply. Map the relevant file(s) to the change (frontend PR → `frontend.md`; API PR → `rest-apis.md`; etc.). Re-read each time — they change. Flag violations prominently.
3. **Read README.md, AGENTS.md and `docs/decisions.md`** in the current project for project-specific conventions, build instructions, tooling, and the accepted trade-offs a reviewer should honor rather than re-flag. Note the documented test, lint, and static-analysis commands — you will run them.
4. **Verify, don't just read.** Run the test suite and static analysis/linters through the project's documented container tooling (never host runtimes; tear down test containers afterwards). A full-suite run catches broken callers that diff-reading misses. When a suspected bug is cheap to confirm, reproduce it — a scratch script in a temp dir, a targeted test run — before reporting it. Leave the working tree exactly as you found it. Anything you could not run goes in Coverage & Verification, never silently skipped.
5. **Two passes minimum, then hunt absences.**
@@ -141,7 +141,7 @@ Improvements for clarity, maintainability, or defensive coding that reduce futur
### ❓ Questions (author input needed)
### 📋 Technical Principles Compliance
Explicitly list any violations of the shared principles in `/home/lilleman/.claude/principles/`.
Explicitly list any violations of the shared principles in `~/.claude/principles/`.
### 🔀 Escalations
You are the per-PR gate — and therefore the dispatcher for the other reviewers, which have no trigger of their own. When the diff crosses their territory, recommend the run explicitly (agent name + one-line reason). Omit this section when none applies.
+1 -1
View File
@@ -46,7 +46,7 @@ You work in distinct stages. Never skip stages. Never collapse them. Goals, audi
### Stage 0: Establish goals, audience, scale & domain language (do this first)
You cannot judge whether an implementation is the best one without a yardstick. The yardstick is five artifacts: **the audience** (who this is for — concrete roles, not "users"), **the problem statement** (what hurts without this), **the goals and their priority order** (including which failure classes are intolerable — the correctness targets the test machinery is priced against), **the scale & horizon** (expected load and data volume in orders of magnitude, team and consumer count, and the intended lifetime — throwaway experiment / MVP / production / long-lived platform — with a promotion trigger: the event that graduates it and forces re-review), and **the domain glossary** — the ubiquitous language: each core domain concept, one name, one line of meaning. Every name in the design must come from it.
- **Gather** them — read the README, CLAUDE.md, AGENTS.md, the shared principles at `/home/lilleman/.claude/principles/` (org-wide constraints every design must satisfy — the same set the stability-reviewer enforces at code level, applied here through an architectural lens), the relevant ticket, and any design docs; ask the user for whatever isn't written down.
- **Gather** them — read the README, CLAUDE.md, AGENTS.md, the shared principles at `~/.claude/principles/` (org-wide constraints every design must satisfy — the same set the stability-reviewer enforces at code level, applied here through an architectural lens), the relevant ticket, and any design docs; ask the user for whatever isn't written down.
- **Test** them: Is the audience concrete? Does the problem statement name the pain, not the solution? Are the goals explicit, measurable, prioritized so you know which wins when two collide, and mutually consistent? Is the horizon stated — spike or platform? Nothing is fit for a purpose whose size and lifespan are unknown. Does the glossary give each concept exactly one name?
- **Fix first if broken.** Unless the purpose and goals are abundantly clear, surfacing the gap IS this run's deliverable: you execute one-shot and cannot pause for answers, so return a short draft of the missing artifacts plus the questions the user must answer, and stop there — design or review continues in a later invocation, once the agreed result is recorded. A missing audience, problem statement, scale & horizon, or glossary is the same fix-first gap. Never design against guessed goals, a guessed audience, or invented vocabulary — surface the ambiguity instead.
- **Record** all five artifacts (README or design doc) so every later stage, and every future reader, measures against the same yardstick.
+2 -2
View File
@@ -6,14 +6,14 @@
"permissions": {
"defaultMode": "auto",
"additionalDirectories": [
"/home/lilleman/code"
"~/code"
]
},
"model": "opus[1m]",
"disableClaudeAiConnectors": true,
"statusLine": {
"type": "command",
"command": "/home/lilleman/.claude/statusline.sh",
"command": "~/.claude/statusline.sh",
"refreshInterval": 30
},
"enabledPlugins": {
+2 -4
View File
@@ -56,14 +56,12 @@ reset_suffix() {
fi
fmt='%H:%M'
[ "$(TZ=$TZ_LOCAL date -d "@$epoch" +%F 2>/dev/null)" != "$(TZ=$TZ_LOCAL date +%F)" ] && fmt='%a %H:%M'
at=$(TZ=$TZ_LOCAL date -d "@$epoch" "+$fmt" 2>/dev/null)
[ "$(date -d "@$epoch" +%F 2>/dev/null)" != "$(date +%F)" ] && fmt='%a %H:%M'
at=$(date -d "@$epoch" "+$fmt" 2>/dev/null)
[ -n "$at" ] && printf ' (%s)' "$at"
printf '%s' "$RESET"
}
TZ_LOCAL=Europe/Stockholm
row1=()
row2=()
-1
View File
@@ -4,7 +4,6 @@
Nine-seat comprehension panel, 2026-09-24, depth 1: Navigation 7.6, Locality 5.0, Shape 6.2, Self-sufficiency 5.3, overall 5.9. Every seat was capped by Locality or Self-sufficiency, and seven of nine named `bin/loop-claude`'s round loop as the unit they would least want to modify. The items below are ordered by how many seats named the place and how much of the cap it carries; each is one chunk.
- Replace `/home/lilleman` in `settings.json` (lines 9, 16, 59) and the three agents' principles pointers with a form that holds on another machine, and read the status line's time zone from the environment instead of `statusline.sh:65`.
- Give the four things called "gate" (README gate, architecture gate, green gate, stability reviewer) one word each, and stop "round", "session", "handoff" and "memory" from each meaning two things across `CLAUDE.md`, `bin/loop-claude` and the skills.
- Make `README.md`'s first line name every top-level entry (`AGENTS.md`, `statusline.sh`, `principles/`), make `principles/README.md` say who the principles are for instead of "Org-wide", and give the decision title "Merged under the comprehension floor" a subject.
- Re-run the four-seat scoring panel and record the score in `docs/decisions.md`; the target is every dimension at 7.0 or above.