Adds one bullet to CLAUDE.md → Working conventions: when an agent finds a defect, flaky test, doc/ADR conflict, or CI problem outside its task, it opens a descriptive issue in the repository the problem belongs to and keeps working. It searches for an existing issue first, marks the issue found-by-claude, leaves it unassigned, and lists what it filed when it reports back.
Requested by the maintainer so findings are tracked where everyone can see them, not lost in chat. The first three are #19 here and Zayin/Ekklesia#97 and #98. The matching platform PR is Zayin/Ekklesia#99.
Docs only; no code or tests change.
Note: ekklesia-bot can open issues and create labels but gets "write permission is required" when applying a label to an issue. Until its team has issue write access, agents mark issues with a footer line instead.
Adds one bullet to `CLAUDE.md` → **Working conventions**: when an agent finds a defect, flaky test, doc/ADR conflict, or CI problem outside its task, it opens a descriptive issue in the repository the problem belongs to and keeps working. It searches for an existing issue first, marks the issue `found-by-claude`, leaves it unassigned, and lists what it filed when it reports back.
Requested by the maintainer so findings are tracked where everyone can see them, not lost in chat. The first three are #19 here and Zayin/Ekklesia#97 and #98. The matching platform PR is Zayin/Ekklesia#99.
Docs only; no code or tests change.
Note: `ekklesia-bot` can open issues and create labels but gets "write permission is required" when applying a label to an issue. Until its team has issue write access, agents mark issues with a footer line instead.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
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 <[email protected]>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Adds one bullet to
CLAUDE.md→ Working conventions: when an agent finds a defect, flaky test, doc/ADR conflict, or CI problem outside its task, it opens a descriptive issue in the repository the problem belongs to and keeps working. It searches for an existing issue first, marks the issuefound-by-claude, leaves it unassigned, and lists what it filed when it reports back.Requested by the maintainer so findings are tracked where everyone can see them, not lost in chat. The first three are #19 here and Zayin/Ekklesia#97 and #98. The matching platform PR is Zayin/Ekklesia#99.
Docs only; no code or tests change.
Note:
ekklesia-botcan open issues and create labels but gets "write permission is required" when applying a label to an issue. Until its team has issue write access, agents mark issues with a footer line instead.🤖 Generated with Claude Code