respond-to-code-review
Answer a Tessl Code Review on a pull request the responder authored. Decides what each finding deserves, fixes, refutes, or declines it with a reason, replies on the thread, and keeps the pull request doing what it was opened to do. Use when review feedback has arrived on an open pull request and the responder is the one answering it, for example "address the review", "respond to the findings", "Tessl left comments", "deal with the review comments", "the check is red and there are findings", or when review rounds keep coming and are not converging. Not for performing a review of someone else's change; that is tessl code review.
95%
Does it follow best practices?
Impact
98%
1.08xAverage score across 18 eval scenarios
Low
Low-risk findings worth noting
The canonical home for this skill is tessl/code-review
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 monitors and processes code review comments and pull requests from GitHub, which can contain outsider-authored free text.
- Repository
tesslio/product-plugins
- Revision
84360a8
- 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.