Use when reviewing a pull request - security-focused review following repo agent guidance for breaking changes, malicious patterns, and backward compatibility
72
88%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
High
Do not use without reviewing
Security
1 high severity finding. You should review these findings carefully before considering using this skill.
The skill handles credentials insecurely by requiring the agent to include secret values verbatim in its generated output. This exposes credentials in the agent’s context and conversation history, creating a risk of data exfiltration.
The skill explicitly injects the full PR diff into external model prompts (e.g., $(gh pr diff ...)) so any secrets present in diffs would be passed into and likely echoed by the LLMs, creating a direct secret-exfiltration risk.
Low
Low-risk findings.
1 low severity finding. Worth noting, but not necessarily harmful.
The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.
The workflow instructs running AI tools with `$(gh pr diff <number> --repo ...)` embedded directly into the Gemini/Codex prompts (Step 4 “Use AI for Deep Analysis” and Step 8 verification), and that diff text originates from an outsider’s PR contents, which can contain free-form malicious payloads that get read into the LLM context.
a8b696d
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.