​

LexCoding Skill Triggers

​

PR Review Sync Requests

• If a user asks to fetch/view/sync/refresh PR comments, review comments, review threads, or unresolved review items (for example “拉取最新 PR 评论”, “看看 review 评论”), treat it as a fetch-pr-reviews request.
• For comment-sync/read requests, run fetch-pr-reviews first.

​

Thread Resolution Requests

• If a user message contains TH-<digits> (for example TH-2780866886), treat it as a request to resolve a PR review thread.
• Default workflow: use resolve-pr-comments in proposal-only mode (generate/fill S6, then stop for user review).

​

Checklist Freshness Rule

• If .lexcoding/prs/<pr_number>/s5_review_checklist.md or .lexcoding/prs/<pr_number>/s5_unresolved_checklist.md is missing or stale, run fetch-pr-reviews first, then continue with resolve-pr-comments.

​

PR Selection Defaults

• Unless the user specifies a PR number, use the current branch PR.
• If the user asks for the “latest PR” and the current branch has no PR, use the latest OPEN PR and state that assumption.

​

Two-Phase Rule for resolve-pr-comments

• Phase 1: generate/fill S6 proposal and ask the user to review.
• Phase 2: execute code/doc changes only after explicit user approval.
• Do not mark threads as resolved (lexcoding pr sync --state resolved) before implementation is complete and user confirms.
• If the user asks only for “方案/建议/怎么改”, do not execute code changes in the same step.