From bf8ac6c8912e9d617b868a1ea56761a5e855574e Mon Sep 17 00:00:00 2001 From: Tobias Gesellchen Date: Sun, 31 May 2026 13:23:38 +0200 Subject: [PATCH] docs: codify resolution + GitHub-reference conventions in CLAUDE.md Add two working conventions to the Communication style section: - An issue is only "resolved" once the reporter confirms; a merged PR or shipped release is not confirmation. - GitHub's # auto-links to issues and pull requests only, not discussions; use the full discussion URL, and avoid # for security alerts (it would point at an unrelated issue/PR). Both recurred often enough in practice to belong in the always-loaded project instructions rather than only in session memory. Co-Authored-By: Claude Opus 4.8 (1M context) --- CLAUDE.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/CLAUDE.md b/CLAUDE.md index 7a2c48e..4ff9a06 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -227,6 +227,16 @@ When working with a human user in this repo: back to whatever you were doing when the user asks something else. - **Don't substitute assumptions for real information.** When something is unclear, ask or check, rather than guessing and proceeding. +- **An issue is only "resolved" once the reporter confirms.** Prefer + "candidate fix, awaiting reporter confirmation" over "fixed" or + "closed" until the person who reported it says it works. A merged PR + or a shipped release is not confirmation. +- **Mind GitHub's `#` auto-linking.** `#` links to issues and + pull requests only — it does **not** resolve to discussions. For a + discussion, write the full URL + (`https://github.com/gesellix/Bose-SoundTouch/discussions/`). For + security alerts, write e.g. "CodeQL alert 280" (no `#`) or the full + URL, since `#280` would point at an unrelated issue/PR. These principles also apply to other AI assistants pointed at this repo. Tool-specific config dirs (e.g. `.junie/`, `.claude/`) should