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.
Installer avec mon Agent
Copiez cette demande dans votre Agent. Elle contient la page Skill de référence et le manifeste.
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.Votre Agent doit toujours présenter son plan et demander toute confirmation exigée par la politique de sécurité.
Ressources lisibles par les agents
Utilisez ces liens lorsquâun Agent IA, un crawler ou un script a besoin dâun contexte propre au lieu de lire toute la page.
Tester
Utilisation de « respond-to-pr-comments-in-blocklist ». Explain the comment about missing input validation before I decide.
Résultat attendu:
The reviewer is concerned that unchecked input can reach the parser. Recommended action: validate the value before parsing, then test invalid input.
Utilisation de « respond-to-pr-comments-in-blocklist ». Apply the approved fixes and show me the response preview.
Résultat attendu:
- 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.
Utilisation de « respond-to-pr-comments-in-blocklist ». Post the approved replies and resolve their threads.
Résultat attendu:
Posted two agent-labeled replies and resolved one approved thread. One PR-level comment remains open because it has no resolvable thread.
Audit de sécurité
SûrAll 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.
Facteurs de risque
âïž Commandes externes (50)
đ AccĂšs au systĂšme de fichiers (3)
Partager et citer ce rapport
Partagez le rapport dâĂ©valuation versionnĂ©, le badge neutre, la carte intĂ©grable et les citations. Skillstore prĂ©sente les preuves sans dĂ©cider si ce Skill est sĂ»r.
Copier le lien du rapport
https://skillstore.io/skills/warpdotdev-respond-to-pr-comments-in-blocklist/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportBadge Markdown
[](https://skillstore.io/skills/warpdotdev-respond-to-pr-comments-in-blocklist?utm_source=security_passport_badge)Badge HTML
<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>Carte intégrable
<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>Citations académiques (APA · BibTeX · CFF)
Citation APA
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/1Citation BibTeX
@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"
Score Skillstore
Pourquoi ce score Niveau de confiance des preuves: MoyenCe que vous pouvez créer
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.
Essayez ces 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.
Bonnes pratiques
- 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.
Ăviter
- 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.
Foire aux 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?
Détails du développeur
Auteur
warpdotdevLicence
MIT
Révision Skillstore
r1
Avis de version
Lâauteur nâa dĂ©clarĂ© aucune version.
Réf
e5464e662405de6361fdde6b984f9ea865635f64
Récence de maintenance
08/09/2026
Utilisation
0 téléchargements · 0 vues
Structure de fichiers
đ SKILL.md