From 0552442c7cc69976fd86411ead11ccf887d31084 Mon Sep 17 00:00:00 2001 From: ekklesia Date: Tue, 13 Oct 2026 22:58:17 -0500 Subject: [PATCH] docs(claude): file an issue for what you find outside the task Findings that only live in a chat reply get lost. Agents now open a descriptive issue in the repository a problem belongs to (after searching for an existing one), mark it found-by-claude, leave it unassigned, and list what they filed when they report back. Co-Authored-By: Claude Opus 5.5 --- CLAUDE.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/CLAUDE.md b/CLAUDE.md index ffdab92..0cb48c7 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -108,6 +108,13 @@ your own memory of a prior session** — treat stale assumptions as a bug to cat - Never run a database migration automatically (on import, on startup, in a test that isn't explicitly a migration test, or as a side effect of an unrelated command). Migrations are always an explicit, operator-invoked action. +- Report what you find. A defect, flaky test, documentation/ADR conflict, or CI problem outside the + task at hand gets an issue in the repository it belongs to, as soon as you find it. Search for an + existing issue first; something fixed in the same PR goes in that PR's description instead. Be + descriptive: what you saw, the evidence (run and job links, commit, file and line), how to + reproduce it, the impact, and options, and never a secret. Label it `found-by-claude` (an agent + that cannot apply labels ends the body with a line saying so), leave it unassigned, and list what + you filed when you report back. ## Canonical verification commands -- 2.54.0