receiving-code-review
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
60
68%
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
Fix and improve this skill with Tessl
tessl review fix ./eval/local/skills/benchmarks/dependency/superpowers/receiving-code-review/SKILL.mdThe canonical home for this skill is receiving-code-review in obra/superpowers
Low
Low-risk findings.
1 low severity finding. Worth noting, but not necessarily harmful.
W011: Third-party content exposure detected (indirect prompt injection risk).
What this means
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.
Why it was flagged
The skill’s workflow is about handling “External Reviewers” feedback, which at runtime would typically be sourced from outsider-authored review comments/PR discussion text (e.g., GitHub issue/PR comment bodies) that the agent reads and incorporates into the LLM context to “READ: Complete feedback.”
- Repository
- rpamis/comet
- Commit
f329b48
- Audited
- Security analysis
Is this your skill?
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.