Repository navigation
[#3145] Kept 'review-code' read-only after the report and documented its external and merged pull request cases. - #3257
Conversation
…d-only review and documented the external and merged pull request cases.
|
Warning Review limit reached
This review includes 2 billable files and costs up to $0.50.
Reviews can continue after your included limit without a manual trigger. An admin must approve usage-based billing. Or wait 9 minutes for your next included review. View limit details
Comment |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
1 similar comment
|
Code coverage (threshold: 90%) Per-class coverage |
This comment has been minimized.
This comment has been minimized.
|
📖 Documentation preview for this pull request has been deployed to Netlify: https://6ae419e8789e54c5564e3e99--vortex-docs.netlify.app This preview is rebuilt on every commit and is not the production documentation site. |
|
Code coverage (threshold: 90%) Per-class coverage |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #3257 +/- ##
==========================================
- Coverage 92.89% 92.28% -0.62%
==========================================
Files 102 108 +6
Lines 4702 5053 +351
Branches 49 3 -46
==========================================
+ Hits 4368 4663 +295
- Misses 334 390 +56 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Closes #3145
Summary
The
review-codeskill's closing step no longer offers to act. After the report it notes that fixing the findings or posting them to the pull request is a separate request, and the review itself does neither. The "Review code" section ofdevelopment/ai.mdxnow documents the cases where the 3-source order and the verdict don't apply as written.#3256 merged before these 2 review fixes reached it. The skill opens by saying it never edits project files or posts to GitHub, but its last step said "offer to fix them or post them to the pull request. Do neither unless the developer asks". An agent that got a "yes" would then edit files or post comments from inside a skill that promised not to. Separately, the docs described the rule order and the verdict as unconditional. In fact the skill uses another repository's rules (and no checklist) for that repository's PRs, drops the verdict for merged or closed PRs, and skips the lint commands
AGENTS.mdlists as well asahoy lint.After merge, a review run never changes anything, even when the developer asks for a fix afterwards; that becomes a normal follow-up request outside the skill. The procedure and checklist are otherwise unchanged.
Before / After
Changes
.claude/skills/review-code/SKILL.md: reworded the closing line so the follow-up is a separate request..vortex/docs/content/development/ai.mdx: documented the other-repository and merged-PR cases and theAGENTS.mdlint commands. Passesyarn lint-prosewith 0 warnings._baseline/.claude/skills/review-code/SKILL.md: regenerated snapshot. All 163 install scenarios pass.