Skip to content

docs(pr-review): align verification wording with installer smoke #6062

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
huangruiteng merged 2 commits into from
Oct 10, 2026
Merged

docs(pr-review): align verification wording with installer smoke #6062

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
e0fbbe8
docs(pr-review): clarify verified evidence wording
LIHUA919 Oct 10, 2026
c2fde15
Merge main into install review skill smoke fix
LIHUA919 Oct 10, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion skills/loopx-pr-review/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -69,7 +69,7 @@ When `review_action_kind` is null, the row stays in `pull_requests` inventory bu
1. Record the packet's exact head, then follow `review_execution_contract.decision_procedure`:
the current goal and `problem_context` delivery judgment first, including on re-review,
then `evidence_commands` and repository-native validation.
2. Fill `review_plan.result_template`; missing evidence stays `unverified`, never `verified` from metadata or CI.
2. Fill `review_plan.result_template`; missing evidence stays `unverified`; never infer `verified` from metadata or CI.
Execute repository-reuse, default-off, authority and real-path counterfactuals, not prose declarations.
Fill `result.reviewer` per `review_execution_contract.reviewer_declaration`; open with its `body_marker` line.
Read `problem_context.spec_basis`'s specification before the diff, plus any `repository_experience` advice.
Expand Down
Loading