Borrowing it
Nothing to install: this file belongs to EndogenAI/dogma. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/EndogenAI/dogma/main/.github/skills/pr-review-reply/SKILL.mdgit clone --depth 1 https://github.com/EndogenAI/dogmaWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/endogenai/dogma/pr-review-reply)<a href="https://agentmods.dev/skills/endogenai/dogma/pr-review-reply"><img src="https://agentmods.dev/badge/skills/endogenai/dogma/pr-review-reply.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00104 | $0.01555 |
| Opus 5 | $0.00052 | $0.00777 |
| Sonnet 5 | $0.00021 | $0.00311 |
| Haiku 4.5 | $0.00010 | $0.00155 |
Grade A, and why
pr-review-reply scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Review Reply
This skill enacts the Algorithms Before Tokens axiom from MANIFESTO.md: repetitive post-review response workflows are encoded as a script and executed deterministically, not performed manually through the UI with repeated token burn per comment. The post-review loop is governed by AGENTS.md § Verify-After-Act for Remote Writes. When this skill and those documents conflict, the primary documents take precedence.
1. Three Modes
The script supports three modes of operation:
| Mode | When to use | Command |
|---|---|---|
| Single reply | One comment to address | --reply-to <id> --body <text> |
| Single resolve | One thread to close without reply | --resolve <thread-node-id> |
| Batch (preferred) | Multiple comments or resolve-without-reply in one pass | --batch <json-file> |
Always use batch mode when addressing more than one comment. It is more reliable than sequential single calls and produces a single audit trail.
2. Single Reply
uv run python scripts/pr_review_reply.py --pr <num> --reply-to <comment-id> --body "Fixed in <sha>."
For multi-line reply bodies, use batch mode with a JSON file instead of --body — shell quoting and backtick interpolation cause gh to misbehave with multi-line text.
3. Single Resolve
uv run python scripts/pr_review_reply.py --pr <num> --resolve <thread-node-id>
This resolves the thread without posting a reply. Use only when the comment does not warrant a reply (e.g., a nit that was silently fixed).
4. Batch Mode (Preferred)
Write a JSON array to a temp file and pass it with --batch:
# Write the batch file (use a file tool — never heredoc)
# Example contents: .tmp/<branch>/review-replies.json
uv run python scripts/pr_review_reply.py --pr <num> --batch .tmp/<branch>/review-replies.json
Batch JSON format — each entry may contain any combination of reply_to, body, and resolve:
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 8d ago First seen · 195 lines · 104 tokens per session scan A 62c8ec670439
pr-review-reply is a skill published in the GitHub repository EndogenAI/dogma (2 stars, last pushed 14d ago), licensed Apache-2.0. It adds 104 tokens to every session and 1,555 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
open-code-review
Performs AI-powered code review on Git changes using the ocr CLI from alibaba/open-code-review. Use when the user asks to review code, review a pull request, review staged/unstaged changes, review a commit, or compare branches for code quality issues. Produces line-level review comments and can automatically apply…
contribute-to-eliza
Finish and prove a scoped elizaOS GitHub issue, or independently review and repair an open elizaOS pull request. Use when contributing compute to elizaOS by selecting unclaimed work, implementing or reviewing changes, adding real tests and evidence, validating artifacts, or preparing a contribution for maintainer…
github
GitHub operations via gh CLI: issues, PRs, CI runs, code review, API queries. Use when: (1) checking PR status or CI, (2) creating/commenting on issues, (3) listing/filtering PRs or issues, (4) viewing run logs. NOT for: complex web UI interactions requiring manual browser flows (use browser tooling when available)…
git
Git and code hosting platform management — GitHub, GitLab, Codeberg, Forgejo. Zero barrier — install x-cmd and manage repos from the terminal. Use for "git", "github", "gitlab", "repo", "pull request", "code hosting".
meta-codereview-current-diff
Read the current uncommitted diff, run three independent reviewers (safety + tests-coverage + style) in parallel, then arbitrate a single BLOCK / BLOCKWITHOVERRIDE / PASSWITHNOTES verdict. Use before commit when you want a multi-perspective second-opinion instead of a single-reviewer agent loop.
parallel-pr-review
Use when asked to "review the open PRs", review a batch or stack of pull requests, or run a recurring PR-review pass on a repo — especially with many PRs, stacked branches, conflicts, or security-sensitive changes. Covers grouping, fan-out to review subagents, verdict synthesis, and posting.