qodo-pr-resolver
Review and resolve PR issues with Qodo - get AI-powered code review issues and fix them interactively (GitHub, GitLab, Bitbucket, Azure DevOps)
65
80%
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 ./.claude/skills/qodo-pr-resolver/SKILL.mdThe canonical home for this skill is qodo-pr-resolver in qodo-ai/qodo-skills
Low
Low-risk findings.
2 low severity findings. 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
Qodo review comments fetched from the PR/MR (outsider-authored by bots/any third party on the repo) are parsed for “issue description” and especially “agent prompt” (Step 4/Step 6/7), meaning the LLM context is fed that extracted free text at runtime via provider CLI/API comment retrieval.
W012: Unverifiable external dependency detected (runtime URL that controls agent).
What this means
The skill fetches instructions or code from an external URL at runtime, and the fetched content directly controls the agent’s prompts or executes code. This dynamic dependency allows the external source to modify the agent’s behavior without any changes to the skill itself.
Why it was flagged
The skill fetches PR comments at runtime (e.g., via "gh api repos/{owner}/{repo}/pulls/<pr-number>/comments") and then executes the fetched Qodo agent prompts as direct instructions, so external comment content from provider APIs can directly control agent behavior.
- Repository
- nanocoai/nanoclaw
- Commit
641963c
- 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.