ci: flag internal-info leaks in PR review prompt#8990
Merged
Conversation
mr-neptune
force-pushed
the
WCN-850_catch_internal_details
branch
from
c21e530 to
298cb0a
Compare
lcovar
approved these changes
Jun 11, 2026
gokulhost
approved these changes
Jun 11, 2026
mr-neptune
changed the title
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
3 participants
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.
ci: flag internal-info leaks in PR review prompt
Description: This PR adds a guardrail to the BitGoJS automated
@claudecode-review prompt (.github/prompts/code-review.md) to catch internal information that AI coding agents tend to leak into public source. Because BitGoJS is a public repository, agents frequently inject development-process narrative into comments—explaining when, how, or why a change was made—rather than describing what the code does. The change introduces a new "Internal Information Leakage" section instructing the reviewer to flag verification/testing metadata, internal team/system names and codenames, internal ticket IDs or doc links, and how/why rationale in comments, JSDoc, test names, and error/log strings—and to suggest a behavior-only rewrite for each—plus a dedicated item in the review's closing checklist so leaks are surfaced and removed before merge.File changed: .github/prompts/code-review.md
Ticket: WCN-850