Finish a feature — run verification, an adversarial review gate (re-grounded on the original design doc + ticket ACs, not the plan) and a deferral-closure gate, then create the PR, retain learnings, and hand off cleanup to the terminal.
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 ./devflow-plugin/skills/finish-feature/SKILL.mdThe canonical home for this skill is finish-feature in AndreJorgeLopes/devflow
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.
SKILL.md Step 4b instructs the agent to fetch and read outsider-authored free text from the “implementation ticket” via the Atlassian/Jira MCP (ticket acceptance criteria and “Development” field), which is then used by the verifier/debugger subagents for review—i.e., runtime LLM context can include that outsider content.
faa2388
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.