Review a change to a public repository for content written for an internal audience, or content a reader outside the company should not have. Use as one lens in a code review run.
69
84%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Low
Low-risk findings worth noting
Everything committed here is world-readable, including its history, and a commit cannot be recalled once pushed. Review the change for content that assumes a reader inside the company.
Read every added line as a reader outside the company would: someone evaluating the product, a competitor, a search engine.
Prose is not the only surface. Check example values, fixture and eval inputs, configuration fields, commented-out lines, and file and directory names, and read an added file's reason for existing as well as its contents — a file whose purpose is to brief a colleague does not belong here whatever it says.
Report content that only makes sense to a reader inside the company, or that a reader outside it should not have.
Do not report a public product name, a public documentation link, the company's own registry, or a public repository. Do not report a ticket identifier in a commit message, which is out of scope for a lens that reviews file contents. Do not accept, or propose, an exclusion from the published bundle as the fix: an ignore rule controls what is uploaded to the registry and leaves the file in this public repository.
37f0a21
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.