inspector/.claude/skills
Repository files (latest commit first)
Filename Latest commit message Latest commit date
cliffhall 5a1b5900cf docs: a reply does not resolve a review thread
Copilot review round 1 on #2273: the text said only a reply in the thread "can
resolve it", which is wrong — resolution is a separate act (the Resolve
conversation button, or the resolveReviewThread GraphQL mutation) and it is the
reviewer's to make. Reading it as satisfied by the documented REST reply is
exactly the wrong conclusion for a PR whose whole point is what a reply does.

State what the reply actually buys: it is the only thing a reviewer reading that
thread sees, and it is what makes resolving the thread defensible.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017nLLLTGc37hQiC8s3mNyhq
Signed-off-by: cliffhall <cliff@futurescale.com>
2026-09-06 12:34:20 -04:00
..
board-ops docs: address Copilot review round 1 on #2203 2026-09-01 10:10:06 -04:00
issue-create docs: tune skill eval cases and document how to write them 2026-08-31 23:22:25 -04:00
issue-triage docs: tune skill eval cases and document how to write them 2026-08-31 23:22:25 -04:00
local-dev chore: address Copilot review round 3 (#2226) 2026-09-05 17:14:44 -04:00
pr-flow docs: a reply does not resolve a review thread 2026-09-06 12:34:20 -04:00
pre-push-gate docs: rule that a wait is a notification, never a tight poll loop (#2253) 2026-09-06 12:26:01 -04:00
project-structure docs: address Copilot review round 7 on #2203 2026-09-01 12:21:09 -04:00
release chore(deps): address Copilot review round 1 on #2232 2026-09-04 09:06:30 -04:00
test-servers feat(skills): address Copilot review round 1 on #2204 2026-09-04 19:33:51 -04:00
testing Review round 8: using a fixture, not connecting, is the trigger 2026-09-05 18:03:37 -04:00