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 alexeyshishin/as-skill --skill git-pr-descriptiongit clone --depth 1 https://github.com/alexeyshishin/as-skillWrote 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/alexeyshishin/as-skill/git-pr-description)<a href="https://agentmods.dev/skills/alexeyshishin/as-skill/git-pr-description"><img src="https://agentmods.dev/badge/skills/alexeyshishin/as-skill/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.00084 | $0.00747 |
| Opus 5 | $0.00042 | $0.00374 |
| Sonnet 5 | $0.00017 | $0.00149 |
| Haiku 4.5 | $0.00008 | $0.00075 |
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 description from a branch diff
Goal: give the user a ready-made PR description in one step — analysis of the branch's commits and diff against the base branch.
Before starting, read ~/.claude/rules/git-conventions.md — the section on PR structure.
Step 1. Determine the base branch and the current one
git branch --show-current
git symbolic-ref refs/remotes/origin/HEAD 2>/dev/null | sed 's@^refs/remotes/origin/@@'
If origin/HEAD is not determined — ask the user: main or master. Store it as BASE.
Step 2. Gather the material
git log $BASE..HEAD --oneline
git log $BASE..HEAD --stat
git diff $BASE...HEAD --stat
git diff $BASE...HEAD
Study what changed: the file list, the size of the changes, the commit texts.
Step 3. Build the PR title
The title is a Conventional Commit for the intended merge commit:
- if all commits on the branch are
feat—feat(<scope>): <overall feature> - if only
fix—fix(<scope>): <what was fixed> - if mixed — pick the dominant type
Step 4. Build the description
Structure (markdown):
## Why
<1-2 sentences: what problem is being solved, whose pain, links to the issue/ticket>
## What changed
- <bullet per logical change, not per file>
- <another one>
- <another>
## How to verify
<either manual verification steps, or "covered by new tests in X", or "smoke-tested on staging">
## Risks / breaking changes
<either "none", or an explicit list with migration steps>
Closes #N
Step 5. Show and ask
Show the title and description in a block. Ask:
- Accept
- Adjust (specify what)
- Add something (tests, screenshots, migration plan)
Step 6. Publish (optional)
If the user has confirmed and wants to open the PR right now:
- check whether the
ghCLI is available:which gh - if yes —
gh pr create --title "..." --body-file <tmp>with the prepared body - if not — say they need to either install
ghor open the PR via the UI and paste in the description
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 · 84 tokens per session scan A db7f6f7c1a5e
git-pr-description is a skill published in the GitHub repository alexeyshishin/as-skill (4 stars, last pushed 18d ago), licensed MIT. It adds 84 tokens to every session and 747 once invoked, about $0.0004 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
pwp-bootstrap
New project initialization protocol — from empty directory to production-ready foundation in one session. Use this skill whenever the user wants to start a new project, initialize a repo, scaffold an application, or set up a codebase from scratch. Also use when they say 'new project', 'start fresh', 'initialize a…
git-wrapup
Land working-tree changes as logical commits — the work grouped by concern, topped by a release commit (version bump, changelog, regenerated artifacts) and an annotated tag. Verify, commit, tag. Stops at "committed and tagged locally" — no push, no publish. The release-and-publish skill picks up from here. Distilled…
phx-pr-review
Address feedback left on a GitHub pull request: fetch unresolved review threads, make agreed Elixir/Phoenix code fixes, reply, and resolve. Use for a PR URL/number or reviewer comments. NOT for pre-PR review, findings triage, or CI monitoring.
ship
Commit, push, and optionally create or update a PR for the current staged changes. Use when the user asks to "ship", "ship it", "ship changes", "commit push and PR", or "ship this".
branch-and-worktree-workflow
Isolates feature work in its own branch or worktree and integrates it cleanly when done. Use this when starting work that should not disturb the current workspace, when several efforts must proceed in parallel on one repository, or when implementation is finished and the change needs merging, rebasing, or splitting…
git-flow
Use this skill when proposing, reviewing, or troubleshooting git commits, branches, pull requests, or merge strategies in a WrongStack project session. Triggers: user mentions "commit", "branch", "PR", "merge", "rebase", "stash", "diff".