break-point-probeUse when verifying that a fix actually reaches the bug's break-point in the real runtime path — not just at unit-test level. Primary trigger is bugfix / cross-stack PR review (invoked by kc-pr-review). Also invoke standalone when pressure-testing a fix claim, pre-merge verification of cross-layer wi
kc-pr-announceUse when a feature is complete with PR and demo artifacts (e2e walkthroughs, Loom, screenshots), and user wants to announce on Slack. Triggers on "announce", "post to product", "draft product message", "公告", or after PR + demo completion.
kc-pr-createUse when user says 'create pr', 'open pr', '建立 PR', '開 PR', '發 PR', '送審', or when implementation is complete and changes need a pull request on GitHub.
kc-pr-daemonUse when user says 'start daemon', 'stop daemon', 'daemon status', 'pr daemon', 'daemon config', 'daemon 掛了', 'daemon error', '啟動 daemon', '停止 daemon', 'daemon 狀態', or wants to manage, configure, or troubleshoot the PR review closed-loop daemon.
kc-pr-reorgUse when a feature branch has messy interleaved commits that need reorganization into logical groups before PR review. Triggers include "squash commits", "clean up history", "reorganize commits", "reorder commits", "too many commits". Not for simple squash-all — use git merge --squash instead.
kc-pr-review-resolveUse when a GitHub PR has review comments or automated feedback that needs triage, validation, and structured response before pushing fixes.
kc-pr-reviewUse when reviewing a GitHub PR and posting inline review comments. Triggered by PR number, PR URL, 'review this PR', 'review current branch PR'.