llmlb: Skill for Gemini CLI

.gemini/skills/gwt-pr-check/SKILL.md

gwt-pr-check is a skill for Gemini CLI from akiojin/llmlb. It costs 33 tokens per session (2,815 once invoked), scanned A, original, MIT.

A read-only workflow for checking the status of a GitHub pull request with the `gh` command-line tool. It also checks whether a merged pull request was followed by new commits on the branch.

In plain words
What is it for?
Use it to inspect the current branch's pull request status, including unmerged requests and commits added after merging.
Why use it?
It shows whether work still needs a pull request, a push, or another action without changing branches, files, or pull requests.

Skill for Gemini CLI

Written for Gemini CLI: installed under .gemini/.

This is akiojin/llmlb's own configuration. It tells Gemini CLI how to work on llmlb itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything llmlb configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/akiojin/llmlb/develop/.gemini/skills/gwt-pr-check/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/akiojin/llmlb

Made for: Gemini CLI.

Wrote 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.

agentmods badge for gwt-pr-check

README.md
[![agentmods](https://agentmods.dev/badge/skills/akiojin/llmlb/gwt-pr-check/github.svg)](https://agentmods.dev/skills/akiojin/llmlb/gwt-pr-check)
Your own site
<a href="https://agentmods.dev/skills/akiojin/llmlb/gwt-pr-check"><img src="https://agentmods.dev/badge/skills/akiojin/llmlb/gwt-pr-check/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.

agentmods 80×15 button for gwt-pr-check

Your own site · 80×15
<a href="https://agentmods.dev/skills/akiojin/llmlb/gwt-pr-check"><img src="https://agentmods.dev/badge/skills/akiojin/llmlb/gwt-pr-check.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 33 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,815 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00033 $0.02815
Opus 5.5 $0.00013 $0.01126
Sonnet 5.5 $0.00007 $0.00563
Haiku 4.5 $0.00003 $0.00281

Measured 8d ago against content hash cc22ba3bed48, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

gwt-pr-check 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.gemini/skills/gwt-pr-check/SKILL.md · 339 lines

How it starts

The opening of the file, as written. The whole thing — 339 lines — stays where its author put it; the contents beside it link to each section on GitHub.

GH PR Check

Overview

Check PR status for the current branch with gh and report a recommended next action.

This skill is check-only:

  • Do not create/switch branches
  • Do not push
  • Do not create/edit PRs

Decision rules (must follow)

  1. Resolve repository, head branch, and base branch.
    • head: current branch (git rev-parse --abbrev-ref HEAD)
    • base: default develop unless user specifies
  2. Optionally collect local working tree state:
    • git status --porcelain
    • Report as context only; do not mutate files.
  3. Fetch latest remote refs before comparing:
    • git fetch origin
  4. List PRs for head branch:
    • gh pr list --head <head> --state all --json
    • number,state,mergedAt,updatedAt,url,title,mergeCommit,baseRefName,headRefName
  5. Classify:
    • No PR found -> NO_PR + recommended action CREATE_PR
    • Any PR where mergedAt == null -> UNMERGED_PR_EXISTS + recommended action PUSH_ONLY
    • All PRs merged -> perform post-merge commit check
  6. Post-merge commit check (critical when all PRs are merged):
    • Select latest merged PR by mergedAt
    • Get merge commit SHA from mergeCommit.oid
    • Verify merge commit ancestry before counting:
      • git merge-base --is-ancestor <merge_commit> HEAD
    • If merge commit is ancestor of HEAD, count commits after merge:
      • git rev-list --count <merge_commit>..HEAD
    • If count > 0 -> ALL_MERGED_WITH_NEW_COMMITS + CREATE_PR
    • If count == 0 -> ALL_MERGED_NO_NEW_COMMITS + NO_ACTION
  7. Fallback when merge commit SHA is missing or not an ancestor of HEAD:
    • First compare against branch upstream (preferred):
      • git rev-list --count origin/<head>..HEAD
    • Count > 0 -> ALL_MERGED_WITH_NEW_COMMITS + CREATE_PR (fallback)
    • Count == 0 -> ALL_MERGED_NO_NEW_COMMITS + NO_ACTION (fallback)
    • If upstream comparison fails, compare against base:
      • git rev-list --count origin/<base>..HEAD
    • If base comparison fails -> CHECK_FAILED + MANUAL_CHECK

Read the full file on GitHub · 339 lines

Changes

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.

  1. 8d ago First seen · 339 lines · 33 tokens per session scan A cc22ba3bed48

Subscribe to this mod's changes

gwt-pr-check is a skill published in the GitHub repository akiojin/llmlb (10 stars, last pushed 3d ago), licensed MIT. It adds 33 tokens to every session and 2,815 once invoked, about $0.0001 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.

Related

Other skills, from other repositories

pr

Draft a PR body from OMC's paper trail — the smallest visual that proves the change, evidence consumed from the verify protocol (never re-collected), reversibility from the ADR test on the diff, glossary language throughout.

Yeachan-Heo/oh-my-claudecode · 47 tokens

merge-batch

Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.

diegosouzapw/OmniRoute · 46 tokens

otto-pr-review-loop

Run Polly and OCR on a PR until all findings settle.

omnigent-ai/omnigent · 17 tokens

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.

Gentleman-Programming/engram · 37 tokens

github-contributor

A step-by-step guide for contributing code, tests, documentation, or build changes to open-source projects you do not maintain. It explains how to prepare a pull request that follows the project’s rules and is easier for maintainers to review.

daymade/claude-code-skills · 105 tokens

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…

umputun/revdiff · 248 tokens