feat(code-review): add github review skill#4166
Open
alex-alecu wants to merge 1 commit into
Open
Conversation
Contributor
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Files Reviewed (4 files)
Reviewed by gpt-5.4-2026-03-05 · Input: 149.6K · Output: 23.8K · Cached: 1.5M Review guidance: REVIEW.md from base branch |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
GitHub Code Reviewer runs now get a trusted skill that tells the agent how to read fresh pull request state and avoid old findings. The skill is added only for GitHub reviews and replaces any skill data sent by the caller, so GitLab reviews keep their current flow. It tells the reviewer to read every page of GitHub data, check the latest commit before writing, ignore stale line comments, and update the Kilo summary with only current issues.
Verification
Visual Changes
N/A
Reviewer Notes
No GitHub issue was listed in the plan. The main risk is prompt behavior: the skill wording should stay aligned with the allowed gh command patterns and the server-owned summary sections.