Borrowing it
Nothing to install: this file belongs to akiojin/llmlb. 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/akiojin/llmlb/develop/.gemini/skills/gwt-fix-pr/SKILL.mdgit clone --depth 1 https://github.com/akiojin/llmlbWrote 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/akiojin/llmlb/gwt-fix-pr)<a href="https://agentmods.dev/skills/akiojin/llmlb/gwt-fix-pr"><img src="https://agentmods.dev/badge/skills/akiojin/llmlb/gwt-fix-pr/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/akiojin/llmlb/gwt-fix-pr"><img src="https://agentmods.dev/badge/skills/akiojin/llmlb/gwt-fix-pr.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.00065 | $0.04410 |
| Opus 5.5 | $0.00026 | $0.01764 |
| Sonnet 5.5 | $0.00013 | $0.00882 |
| Haiku 4.5 | $0.00006 | $0.00441 |
Grade A, and why
gwt-fix-pr 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- gh-fix-pr — 98% identical, 18 lines differ
How it starts
The opening of the file, as written. The whole thing — 489 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Gh PR Checks Plan Fix
Overview
Use gh to inspect PRs for:
- Failing CI checks (GitHub Actions)
- Merge conflicts
- Update Branch requirements (base branch advanced)
- Reviewer comments (review summaries, inline comments, issue comments)
- Change Requests from reviewers
- Unresolved review threads
Then propose a fix plan, implement after explicit approval, reply to every reviewer comment (with action taken or reason for not addressing), resolve all threads, and notify reviewers.
- Depends on the
planskill for drafting and approving the fix plan.
Prereq: ensure gh is authenticated (for example, run gh auth login once), then run gh auth status with escalated permissions (include workflow/repo scopes) so gh commands succeed.
Comment Response Policy
No reviewer comment may be left unanswered.
- Every unresolved review thread MUST receive a reply before being resolved.
- If the feedback was addressed: reply with what was done (e.g., "Fixed: refactored as suggested.").
- If the feedback was intentionally not addressed: reply with the reason (e.g., "Not addressed: this is intentional because the API contract requires this format.").
- The
--reply-and-resolveargument enforces this by requiring a reply entry for every unresolved thread and rejecting empty bodies.
Diagnosis Report Anti-Patterns
Prohibited Language
| Prohibited | Required Alternative |
|---|---|
| "We should look into..." | "Edit path/file.ts:42 to..." |
| "There seem to be some issues" | "3 blocking items detected" |
| "This might be causing..." | "Root cause: <error from log>" |
| "Consider fixing..." / "It looks like..." | "Action: Fix <what> in <where>" |
| "Various CI checks are failing" | "2 CI checks failing: build, lint" |
| "Some reviewers have concerns" | "@reviewer1 requested: <quote>" |
| "I'll try to fix this" | "Action: <specific fix>" |
Structural Prohibitions
- Prose paragraphs for reporting — use B1/I1 item format exclusively.
- Omitting the Evidence field in any BLOCKING item.
- Combining multiple independent problems into a single item.
- Omitting file paths or line numbers when the script output contains them.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 489 lines · 65 tokens per session scan A 4ef9e6d7a793
gwt-fix-pr is a skill published in the GitHub repository akiojin/llmlb (10 stars, last pushed 3d ago), licensed MIT. It adds 65 tokens to every session and 4,410 once invoked, about $0.0003 per session on Opus 5.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-10-21.
Other skills, from other repositories
sync-bridge
Reviews and guides Chromium Sync Model API (DataTypeSyncBridge) implementations, including DataTypeStore persistence and forwards/backwards compatibility for sync specifics. Use when implementing or reviewing a DataTypeSyncBridge subclass, DataTypeStore usage, sync metadata persistence, conflict resolution, or…
sync-model-processor
Reviews changes to Chromium Sync model internals in components/sync/model/, including ClientTagBasedDataTypeProcessor, ClientTagBasedRemoteUpdateHandler, ProcessorEntity, ProcessorEntityMetadata, and ProcessorEntityTracker. Use when modifying or reviewing processor state transitions, entity metadata tracking, conflict…
adversarial-reviewer
Stress-test a code change for concrete correctness defects, unsafe assumptions, and failure modes. Use when the user explicitly asks for an adversarial review, a deep bug hunt, or to tear a change apart, or to check your own change before submitting it. Do not use for ordinary review, style feedback, or general…
gsd-ns-review
Invoke this Pi skill with /skill:gsd-ns-review.
gitnexus
A code-graph analysis add-on for examining an existing codebase, including symbols, call paths, execution flows, and effects across repositories. It can query GitNexus through its command-line or MCP interfaces.
issue
Use when starting a chain from a GitHub issue — turning an issue URL or number into a triaged, planned, dispatched, and reviewed pull request. Classifies the thread (bug → root-cause discipline, feature → plan chain, question → drafted reply), synthesizes a spec from the issue's own acceptance criteria, then runs the…