Vp pr review followup
Reusable Agent Skills by VdustR
npx -y skills add VdustR/skills --skill vp-pr-review-followupAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Follow up on GitHub PR conversations from the reviewer side. Use to verify author replies or fixes, challenge unsupported responses, remind authors, or resolve threads opened by the reviewer. Boundary: authors addressing feedback should use vp-pr-comment-resolver.
SKILL.md
1.4 KB, as published. Nobody here has run it
Pull Request Review Follow-Up
Re-evaluate the original concern against the current head and full conversation. An author reply, emoji, or changed line is not proof that the concern is fixed. Keep reviewer-side follow-up read-only with respect to the author's code and history: do not edit, commit, push, or rewrite the PR branch.
Decisions
- Resolved: the current implementation and verification address the concern.
- Needs follow-up: evidence is incomplete, the fix is partial, or a new risk was introduced.
- No longer applicable: the code or scope changed and the original concern is obsolete.
- Needs user judgment: product or architectural intent remains ambiguous.
Reply on the original surface with concrete evidence and a clear next action. Resolve only threads the acting reviewer owns and only after the concern is actually closed. Inspect later discussion to avoid duplicate or contradictory replies.
Read references/workflow.md for state transitions and
references/reply-templates.md for concise response shapes.