respond-to-pr-comments-in-blocklist
Resolve Pull Request Feedback Safely
Pull request feedback can be difficult to track, implement, and answer consistently. This skill guides each decision, validates accepted changes, and previews GitHub responses before posting.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "respond-to-pr-comments-in-blocklist" from https://skillstore.io/skills/warpdotdev-respond-to-pr-comments-in-blocklist.md and its manifest at https://skillstore.io/api/skills/warpdotdev-respond-to-pr-comments-in-blocklist/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "respond-to-pr-comments-in-blocklist". Explain the comment about missing input validation before I decide.
Expected outcome:
The reviewer is concerned that unchecked input can reach the parser. Recommended action: validate the value before parsing, then test invalid input.
Using "respond-to-pr-comments-in-blocklist". Apply the approved fixes and show me the response preview.
Expected outcome:
- Comment 1: reply and resolve. Draft reply explains the added validation and successful focused test.
- Comment 2: reply only. Draft reply records the decision to preserve current behavior.
- No GitHub actions have been posted.
Using "respond-to-pr-comments-in-blocklist". Post the approved replies and resolve their threads.
Expected outcome:
Posted two agent-labeled replies and resolved one approved thread. One PR-level comment remains open because it has no resolvable thread.
Security Audit
SafeAll 55 static findings are false positives caused by Markdown code formatting, relevant GitHub CLI examples, secure temporary files, or GraphQL field names. The workflow gates repository changes, pushes, GitHub replies, and thread resolution behind explicit user decisions and previews.
Risk Factors
โ๏ธ External commands (50)
๐ Filesystem access (3)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/warpdotdev-respond-to-pr-comments-in-blocklist/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/warpdotdev-respond-to-pr-comments-in-blocklist?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/warpdotdev-respond-to-pr-comments-in-blocklist?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/warpdotdev-respond-to-pr-comments-in-blocklist/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/warpdotdev-respond-to-pr-comments-in-blocklist.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA ยท BibTeX ยท CFF)
APA citation
warpdotdev. (2026). respond-to-pr-comments-in-blocklist security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/warpdotdev-respond-to-pr-comments-in-blocklist/audits/1BibTeX citation
@techreport{warpdotdev-warpdotdev-respond-to-pr-comments-in-blocklist-2026,
author = {warpdotdev},
title = {respond-to-pr-comments-in-blocklist security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/warpdotdev-respond-to-pr-comments-in-blocklist/audits/1},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "respond-to-pr-comments-in-blocklist security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "warpdotdev"
date-released: "2026-09-04"
url: "https://skillstore.io/skills/warpdotdev-respond-to-pr-comments-in-blocklist/audits/1"
identifiers:
- type: other
value: "skillstore:warpdotdev-respond-to-pr-comments-in-blocklist:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Address a Small Review
Walk through a few review comments, apply selected fixes immediately, and approve each final response.
Process Large Feedback Batches
Collect decisions across many comments before applying related changes and validating them together.
Close Reviewed Threads
Prepare transparent replies, link pushed fixes when available, and resolve only approved review threads.
Try These Prompts
Walk me through actionable comments on the current pull request one by one. Let me approve each fix before continuing.
Review all actionable pull request comments in batch mode. Collect my decision for each comment before editing any files.
Address accepted review comments, preserve unrelated changes, and run repository-appropriate validation. Prepare concise replies, but do not post them yet.
Process unresolved review feedback, apply approved changes, offer commit and push, then preview replies and resolutions for final approval.
Best Practices
- Inspect referenced code before recommending a fix when the loaded comment lacks enough context.
- Keep every reply concise, specific, and linked to validated work when a pushed commit exists.
- Review the final diff and response preview before approving any GitHub action.
Avoid
- Do not skip uncertain comments merely because they appear automated or previously answered.
- Do not combine unrelated refactoring with changes requested by review comments.
- Do not post replies, resolve threads, commit, or push before the required approval step.
Frequently Asked Questions
Can this skill only display pull request comments?
Will it change code automatically?
Can I review comments in a batch?
Will it commit and push changes?
How are GitHub replies identified?
What happens when a thread cannot be resolved?
Developer Details
Author
warpdotdevLicense
MIT
Skillstore revision
r1
Version notice
The author did not declare a version.
Ref
e5464e662405de6361fdde6b984f9ea865635f64
Maintenance freshness
9/8/2026
Usage
0 downloads ยท 0 views
File structure
๐ SKILL.md