Borrowing it
Nothing to install: this file belongs to deliveryhero/asya. 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/deliveryhero/asya/main/.claude/commands/fix-pr-review-comments.mdgit clone --depth 1 https://github.com/deliveryhero/asyaWrote 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/commands/deliveryhero/asya/fix-pr-review-comments)<a href="https://agentmods.dev/commands/deliveryhero/asya/fix-pr-review-comments"><img src="https://agentmods.dev/badge/commands/deliveryhero/asya/fix-pr-review-comments.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.00011 | $0.01155 |
| Opus 5 | $0.00005 | $0.00577 |
| Sonnet 5 | $0.00002 | $0.00231 |
| Haiku 4.5 | $0.00001 | $0.00115 |
Grade A, and why
fix-pr-review-comments 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 — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Comment Analyzer & Resolver
Analyze all comments on a GitHub pull request, implement changes, and post targeted responses to each review comment using gh CLI.
Usage
Provide a GitHub PR URL or PR number:
/fix-pr-review-comments https://github.com/deliveryhero/asya/pull/119
# or
/fix-pr-review-comments 119
Process
-
Fetch PR Details
- Get PR URL, branch name, current files
- List all comments (review comments and conversations)
-
Analyze Each Comment
- Categorize: bug fix, enhancement, documentation, style/formatting, validation, question
- Assess: actionable vs informational
- Extract key requirements
-
For Actionable Comments
- Implement suggested changes
- Run validation (linting, tests if applicable)
- Create focused, logical commits
- Push to PR branch
-
Post Targeted Responses
- Reply directly to each review comment (not general PR comment)
- Use
gh apito post reply in the specific conversation thread - Keep responses concise and focused on that specific suggestion
- Use
gh apito mark conversation as resolved if applicable
-
No Generic Summaries
- Post targeted, context-specific responses only
- Each suggestion gets a reply in its own thread
- Skip generic summaries - let the implementation speak
Response Format
For each review comment:
- Reply directly in the conversation thread (not new PR comment)
- Keep it very short: "✅ Implemented in commit XYZ - [brief description]" is enough
- Mark conversation as resolved if applicable (via
ghAPI)
Implementation Notes
- Work in the existing branch (don't create new branches)
- Preserve existing commits; append new commits
- Use
gh apito reply to specific review comments (see "Posting Replies" below) - Run quality gates after each logical change group
- Always preserve original PR intent and author's work
Working with Review Threads
GitHub review comments are organized into threads. Use GraphQL API to query and resolve threads.
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 · 178 lines · 11 tokens per session scan A 2b625013826b
fix-pr-review-comments is a command published in the GitHub repository deliveryhero/asya (58 stars, last pushed today), licensed Apache-2.0. It adds 11 tokens to every session and 1,155 once invoked, about $0.0001 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-30.
Other commands, from other repositories
triage
Triages a PR comment — from a bot (Copilot, CI) or a human reviewer. Fetches the comment and diff via gh CLI, classifies it, applies the fix directly to the file if valid, posts a reply on the thread, and resolves it. Run from inside the repo.
pr-manager
Comprehensive pull request management with ruv-swarm coordination for automated reviews, testing, and merge workflows.
pr-enhance
Command "pr-enhance" from shyftlabs/continuum, covering pr-enhance, usage, options, examples and enhance pr.
devkit.github.review-pr
Provides comprehensive GitHub pull request review with code quality, security, and best practices analysis. Use when reviewing a PR before merging.
speckit.spex.submit
Push and create PR for team review, with optional watch mode for CI monitoring.
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.