Borrowing it
Nothing to install: this file belongs to hiromaily/docs-ssot. 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/hiromaily/docs-ssot/main/.agents/skills/fix-pr-reviews/SKILL.mdgit clone --depth 1 https://github.com/hiromaily/docs-ssotWrote 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/hiromaily/docs-ssot/fix-pr-reviews)<a href="https://agentmods.dev/skills/hiromaily/docs-ssot/fix-pr-reviews"><img src="https://agentmods.dev/badge/skills/hiromaily/docs-ssot/fix-pr-reviews/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/hiromaily/docs-ssot/fix-pr-reviews"><img src="https://agentmods.dev/badge/skills/hiromaily/docs-ssot/fix-pr-reviews.svg" alt="Reviewed on agentmods" width="80" 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.00024 | $0.00268 |
| Opus 5 | $0.00012 | $0.00134 |
| Sonnet 5 | $0.00005 | $0.00054 |
| Haiku 4.5 | $0.00002 | $0.00027 |
Grade A, and why
fix-pr-reviews 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 11d 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.
What it actually says
Fix PR review comments
Fix PR review comments
For the current branch, determine the PR number with gh pr view --json number.
Fetch inline review comments (diff comments) with:
gh api repos/{owner}/{repo}/pulls/{pull_number}/comments
These are separate from issue-level comments. Do not use gh pr view --json comments — that field returns only issue-level (non-diff) comments and will miss inline review comments.
For each comment that has not yet been resolved:
- Read the referenced file and line to understand the context.
- Apply the fix directly in the file.
- Reply to the comment using:
Note: the pull number must be included in the path — omitting it returns 404.gh api repos/{owner}/{repo}/pulls/{pull_number}/comments/{comment_id}/replies -f body="<reply>"
After all comments are addressed, stage and commit the changes, then push the branch.
Keep replies short and factual: what was changed and why. Do not ask for confirmation before fixing — just fix and reply.
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.
- 11d ago First seen · 31 lines · 24 tokens per session scan A e564e87edf6d
fix-pr-reviews is a skill published in the GitHub repository hiromaily/docs-ssot (2 stars, last pushed 5mo ago), licensed MIT. It adds 24 tokens to every session and 268 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-31.
Other skills, from other repositories
review-implement-phase
Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.
engram-branch-pr
PR creation workflow for Engram following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.
verify-behavior
Verify or reproduce visible product behavior by driving the real UI with pi-computer-use's checked tools, requiring verified expect postconditions and durable state evidence for meaningful UI flows. Use when triage needs visual reproduction, implementation needs behavioral proof, review needs interactive confirmation…
github-contributor
End-to-end playbook for shipping high-quality pull requests to open-source projects you don't maintain — discovery, CONTRIBUTING compliance, PR-size check, minimal-diff implementation, PR description with AI-assisted disclosure, conflict resolution, and post-submission maintainer interaction. Use whenever creating…
revdiff
Review diffs, files, and documents with inline annotations in a TUI overlay, or answer questions about revdiff usage, configuration, themes, and keybindings. Opens revdiff in agterm/tmux/zellij/herdr/kitty/wezterm/cmux/ghostty/iterm2/emacs-vterm, captures annotations, and addresses them. Works in git, hg, and jj repos…
oss-maintainer
Run an open-source project's issue/PR/release loop like a careful human maintainer — triage to root cause, absorb community PRs before duplicating them, gate every merge, ship honest releases, and thank the people doing your QA for free.