# Pr Review Comment

> Convert <final_review> XML from the pr-review workflow into a human-readable Markdown comment and post it to GitHub via gh. Use when: (1) the orchestrator or user requests `/pr-review-comment`, (2) a non-XML PR review comment must be published from a <final_review> payload, or (3) a follow-up step needs to post review results directly to a PR.

- Skill: `hansjm10/pr-review-comment` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add hansjm10/pr-review-comment`
- Raw SKILL.md: https://api.skillmd.com/api/skills/hansjm10/pr-review-comment/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Docs & Writing
- Author: hansjm10 (https://skillmd.com/u/hansjm10)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/hansjm10/pr-review-comment

---


# PR Review Comment Publisher

## Workflow

1. Receive inline <final_review> XML from the pr-review workflow.
2. Convert XML sections to Markdown, omitting empty sections.
3. Post the Markdown as a PR comment using `gh pr comment`.

## Usage

Preferred (owner/repo#PR):

```bash
python /codex/skills/pr-review-comment/scripts/post_comment.py --pr owner/repo#123 <<'XML'
<final_review>
  ...
</final_review>
XML
```

If already in the repo:

```bash
python /codex/skills/pr-review-comment/scripts/post_comment.py --pr 123 <<'XML'
<final_review>
  ...
</final_review>
XML
```

Optional override:

```bash
python /codex/skills/pr-review-comment/scripts/post_comment.py --repo owner/repo --pr 123 <<'XML'
<final_review>
  ...
</final_review>
XML
```

## Section Mapping

- `changed_files_ref` → "Changed Files"
- `requirements_ref` → "Requirements"
- `summary` → "Summary"
- `blockers` → "Blockers"
- `non_blocking_suggestions` → "Non-blocking Suggestions"
- `test_gaps` → "Test Gaps"
- `documentation_gaps` → "Documentation Gaps"
- `actionable_outcomes` → "Actionable Outcomes" (one bullet per task with priority/effort, why, files, change)
- `questions_for_author` → "Questions for Author"
- `merge_recommendation` → "Merge Recommendation"

## Notes

- Input must be well-formed `<final_review>` XML and is read from stdin.
- Requires an authenticated `gh` CLI with access to the target repo.
- Use `--print-only` to render the Markdown without posting.