Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add jtprogru/bear-skills --skill git-pr-descriptiongit clone --depth 1 https://github.com/jtprogru/bear-skillsWrote 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/jtprogru/bear-skills/git-pr-description)<a href="https://agentmods.dev/skills/jtprogru/bear-skills/git-pr-description"><img src="https://agentmods.dev/badge/skills/jtprogru/bear-skills/git-pr-description.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.00095 | $0.00851 |
| Opus 5 | $0.00048 | $0.00426 |
| Sonnet 5 | $0.00019 | $0.00170 |
| Haiku 4.5 | $0.00010 | $0.00085 |
Grade A, and why
git-pr-description 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 6d 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
git-pr-description — Описание PR из diff ветки
Цель: дать пользователю готовое описание PR в один шаг — анализ коммитов и diff ветки против базовой ветки.
Перед началом прочитай ~/.claude/rules/git-conventions.md — раздел про структуру PR.
Шаг 1. Определи базовую ветку и текущую
git branch --show-current
git symbolic-ref refs/remotes/origin/HEAD 2>/dev/null | sed 's@^refs/remotes/origin/@@'
Если origin/HEAD не определена — спроси пользователя: main или master. Запомни как BASE.
Шаг 2. Собери материал
git log $BASE..HEAD --oneline
git log $BASE..HEAD --stat
git diff $BASE...HEAD --stat
git diff $BASE...HEAD
Изучи, что менялось: список файлов, размер изменений, тексты коммитов.
Шаг 3. Сформируй заголовок PR
Заголовок — Conventional Commit для предполагаемого merge-коммита:
- если все коммиты ветки
feat—feat(<scope>): <общая фича> - если только
fix—fix(<scope>): <что починили> - если разные — выбери доминирующий type
Шаг 4. Сформируй описание
Структура (markdown):
## Зачем
<1-2 предложения: какая проблема решается, чья боль, ссылки на issue/тикет>
## Что изменилось
- <буллет по логическому изменению, не по файлу>
- <ещё один>
- <ещё>
## Как проверить
<либо шаги для ручной проверки, либо «покрыто новыми тестами в X», либо «smoke в стейджинге»>
## Риски / breaking changes
<либо «нет», либо явный список с миграцией>
Closes #N
Шаг 5. Покажи и спроси
Покажи заголовок и описание в блоке. Спроси:
- Принять
- Поправить (что именно)
- Добавить чего-то (тесты, screenshots, migration plan)
Шаг 6. Опубликуй (опционально)
Если пользователь подтвердил и хочет открыть PR прямо сейчас:
- проверь, есть ли
ghCLI:which gh - если есть —
gh pr create --title "..." --body-file <tmp>с подготовленным телом - если нет — скажи, что нужно либо
ghпоставить, либо открыть PR через UI и вставить описание
Не пушь ветку самостоятельно, если она ещё не запушена. Покажи пользователю команду git push -u origin <branch> и дай ему решить.
What ships with it
1 file 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.
- 6d ago First seen · 92 lines · 95 tokens per session scan A 7ef6674fb973
git-pr-description is a skill published in the GitHub repository jtprogru/bear-skills (1 stars, last pushed 19d ago), licensed MIT. It adds 95 tokens to every session and 851 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
OCR Review-to-Approval Loop
Drive a PR to an approved code review by looping OCR's multi-agent review and address steps. Runs /ocr:review then /ocr:address repeatedly until the review verdict is APPROVE, then one final /ocr:address for leftover suggestions, posting every review and every address round to the GitHub PR as comments. Use when the…
avatar-contribution-pr
Turn an avatar GitHub issue (from the in-app avatar-editor easter egg) into a merged sprite — validate the art, then either add a new module or replace an existing one, and open a PR that closes the issue. Handles both "Avatar contribution: " (a brand-new sprite) and "Avatar edit: " (a hand-redraw of an existing…
loop-on-ci
Monitor PR checks and fix failures until green. Uses gh pr checks as the source of truth for PR-attached checks.
working-in-grove
Use when you are the coding agent running INSIDE a Grove workspace — a git worktree Grove created for one task, on the host or in a container. Triggers on: reporting or updating your task phase or progress, GROVEPHASEFILE or .grove/phase.json, grove phase, grovesetworkspacephase, naming this workspace or setting its…
rollback
A tool for undoing recent automatic changes or the changes associated with a named proposal, using recorded backups.
configuring-grove
Use when a user wants to set up or change Grove's configuration, for a host/user or for a project. Covers the global user config, the committed project config, machine-local overrides, agents, init scripts, containers, tmux and peek tuning, the TUI theme, the daemon auth, notifications, and ticket providers (Gitea…