Skip to content
Back to skills

Specialist Pr Commenter Batch

ASecurity

Posts sanitized batches of PR review comments or replies through configured review tooling. Use after review-ticket when findings are approved for publication.

  • 549 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added June 6, 2026
developmentgitapi

Works with

  • api
  • mcp

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned October 3, 2026

npx -y skills add HoangNguyen0403/agent-skills-standard --skill specialist-pr-commenter-batch --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Specialist Pr Commenter Batch?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Specialist Pr Commenter Batch
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/hoangnguyen0403-specialist-pr-commenter-batch/badge)](https://www.skillsdirectory.com/skills/hoangnguyen0403-specialist-pr-commenter-batch)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: specialist-pr-commenter-batch
description: Posts sanitized batches of PR review comments or replies through configured review tooling. Use after review-ticket when findings are approved for publication.
metadata:
  internal: true
  triggers:
    keywords:
      - batch PR comments
      - post review findings
      - resolve PR threads
      - ADO comments
      - GitHub comments
      - GitLab comments
---
# Specialist: PR Commenter Batch

## **Priority: P1 (HIGH)**

## Role

Post multiple approved review comments safely and report result status.

## Budget

- Execute only from explicit comment specs.
- Use ADO/GitHub/GitLab MCP when configured.
- Do not read PR state unless caller asks.
- No sub-agents.
- If no approved comment specs are supplied, or no posting MCP is configured, return `BLOCKED` instead of guessing content.

## Sanitization

1. Reject markdown image embeds in comments.
2. Strip mass mentions: `@all`, `@team`, `@everyone`.
3. Cap comment body at 8KB.
4. Reject absolute paths and `..` in inline file paths.
5. Post independent comments in parallel when runtime supports it.

## Output

```text
| # | Mode | Target | Result |
| --- | --- | --- | --- |
| [n] | [new/reply] | [file/thread] | [posted/rejected] |
```

## Anti-Patterns

- No unsanitized posting.
- No generated findings; caller supplies approved comments.
- No raw API JSON.

Files in this skill

  • SKILL.md1.2 KB
  • evals/evals.json620 B

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.