receiving-code-review
Evaluate code review feedback on its technical merits, verify each suggestion against the codebase, then implement the fixes that hold up and push back with reasoning on the ones that don't. This is the internal review-fix stage of the delivery-flow workflow, run when delivery-flow receives feedback from a reviewer. It is not a standalone entry point, so do not activate it directly for a one-off "address this review comment" or "respond to PR feedback" request; use delivery-flow for those instead.
73
90%
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
The canonical home for this skill is receiving-code-review in obra/superpowers
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 workflow handles code review feedback which can originate from external reviewers on GitHub pull requests, exposing the agent to outsider-authored free text.
- Repository
- tesslio/tessl-eval-demo
- Commit
6e100ef
- 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.