plan-pr
Turn a prompt, bug report, issue ID, or ticket URL into a repository-grounded implementation plan for human approval. Use when the user asks to plan a PR, prepare a ticket for implementation, work out how to build a feature, or set up the plan-pr workflow. Reads tracker context and repo rules, routes to a fixed set of design and TDD skills, and defines observable acceptance criteria. After approval the same agent implements, then invokes ship-pr-dev. For shipping an existing branch or fixing PR CI without a planning request, use ship-pr-dev directly.
74
92%
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
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 required workflow reads tickets, comments, and issue tracker content via external provider URLs and references, which allow outsider-authored free text to be ingested into the agent's context.
- Repository
- The-Vibe-Company/companion
- Commit
c950f6f
- 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.