Handle unresolved review threads on a PR in units of 1 commit = 1 logical change. This file shows the entry point and how to read through it, while procedures, boundary conditions, and reply rules are separated into references.
Reference files
- review-intake-and-scope.md: Bot gate at start, thread collection, scope inside and outside the PR
- review-group-classification.md: When classifying unresolved threads into logical change groups
- group-commit-reply-sequence.md: Order of implementation, atomic commit, push, and individual reply for each group
- validation-checklist.md: Consistency and traceability checks after all groups are complete
How to read through
- At start, read review-intake-and-scope.md to determine the Bot write gate, target PR, threads, and boundaries of target files.
- After listing threads, read review-group-classification.md to determine the list of logical groups before working.
- Before implementing each group, read group-commit-reply-sequence.md to confirm horizontal expansion to all files in the PR and handling of candidates outside the PR.
- Before completion, read validation-checklist.md to confirm the status of commits, replies, and resolves.
Final check
- Bot write gateと
kf-g-github-operations-bot-workflowsatisfies the delegation path to . - Check all target files in the PR without omission, and hold changes outside the PR until user confirmation.
- Each commit is one logical change, and after pushing, reply individually to each thread.
- Treat resolve as something the user does, and report unresolved threads and the correspondence table.
- validation-checklist.md Check all items of .