From be809b4556f68ad7887cbe778bd89be2cd440735 Mon Sep 17 00:00:00 2001 From: Marius Bughiu Date: Wed, 22 Jul 2026 09:03:56 +0300 Subject: [PATCH] docs(claude): require replying to and resolving PR review comments you act on Codify the review-response workflow: whenever you address a PR review comment, reply with your conclusion (agree or not, and what changed, referencing the commit) and mark the thread resolved, so it's always clear which comments are handled and which are still open. Co-Authored-By: Claude Opus 4.8 (1M context) --- CLAUDE.md | 1 + 1 file changed, 1 insertion(+) diff --git a/CLAUDE.md b/CLAUDE.md index e5a31e2..5fc8905 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -62,3 +62,4 @@ Too verbose (avoid): a full paragraph reciting the `(uint)index >= (uint)_length - Conventional-commit style subjects (`perf(BitSet): …`, `fix(...)`, `docs(...)`). - Bug fixes ship with a regression test that fails on `main`. - Never add `` / `` / `` to any `.csproj` — MinVer owns versioning from git tags. +- When you act on a PR review comment, always **reply to that comment** with your conclusion — whether you agree or not, and what you changed (reference the commit) — **and mark the thread resolved**. Do this for every comment you address, so it's clear which are handled and which are still open. If you disagree and make no change, still reply with the reasoning and leave the thread unresolved for the maintainer to decide.