Repository navigation
Conversation
Contributor
🔒 PR Risk Scan ResultsScanned 1 changed file(s).
✅ No matching risk patterns were detected in changed files.
|
Contributor
|
🟡 Contributor Reputation Check: MEDIUM risk
Maintainers: please review this contributor before merging. |
Contributor
🚦 Submission status: 👀 Ready for reviewRisk tier: Why this tier
Automated checks
Review
Commands
Updated for |
This branch has not been deployed
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.
Adds
instructions/code-review-falsifiable-findings.instructions.mdand the regenerateddocs/README.instructions.mdrow (npm start).What it does: steers Copilot code review away from speculative comments. Each finding must give the file and line, a concrete triggering input, the expected result, the predicted result, and the smallest test that fails today. Items without a trigger are labeled
question; untraced paths are labelednot traced; the review ends with the three highest-risk findings, what was not reviewed, and one decision.Why it is not a duplicate of
code-review-generic: that file covers what to look for (priorities, security, quality). This one constrains the shape of each finding so a human can confirm or reject it with one test, which matters most for AI-generated patches that pass the obvious case and fail at a boundary.Usage notes: uses
excludeAgent: 'cloud-agent'so it applies to code review only (value checked against the current GitHub custom-instructions docs). Treats the PR description as the change's intent.Testing / disclosure: the frontmatter and format follow the docs and the README was regenerated with
npm start. I have not run it against a live Copilot code review session. The same rules are published as an MIT repo at https://github.com/itscloud0/ai-code-review-prompt, which I maintain. Prepared by an AI coding agent on my behalf.