Borrowing it
Nothing to install: this file belongs to PedroMosquera/squadai. 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/PedroMosquera/squadai/main/.claude/skills/pr-description/SKILL.mdgit clone --depth 1 https://github.com/PedroMosquera/squadaiWrote 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/pedromosquera/squadai/pr-description)<a href="https://agentmods.dev/skills/pedromosquera/squadai/pr-description"><img src="https://agentmods.dev/badge/skills/pedromosquera/squadai/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.00003 | $0.00474 |
| Opus 5 | $0.00002 | $0.00237 |
| Sonnet 5 | $0.00001 | $0.00095 |
| Haiku 4.5 | $0.00000 | $0.00047 |
Grade A, and why
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 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.
How it starts
The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: pr-description description: Generate pull request descriptions from diff analysis
PR Description Skill
Generate a clear, reviewer-friendly pull request description by analyzing the diff and commit history. Follow this protocol for consistent output.
Steps
-
Analyze the diff: Read all changed files to understand the scope.
- What files were added, modified, or deleted?
- What is the primary purpose of the change?
- Are there multiple logical changes bundled together?
-
Identify the change type: Classify the PR.
- Feature: New functionality or capability.
- Fix: Bug fix or error correction.
- Refactor: Code restructuring without behavior change.
- Docs: Documentation updates.
- Test: Test additions or improvements.
- Chore: Build, CI, dependency, or tooling changes.
-
Write the summary: Create 1-3 bullet points.
- Focus on what changed and why, not how.
- Lead with the most important change.
- Keep each bullet to one sentence.
-
List the changes: Group modifications by area.
- Group related files together (e.g., "API endpoints", "Database models").
- Describe what changed in each group, not file-by-file.
- Note any new dependencies or configuration changes.
-
Describe testing: Explain what was verified.
- What tests were added or updated?
- How can a reviewer verify the change manually?
- Are there any known limitations or untested scenarios?
-
Note breaking changes: Flag anything that affects existing behavior.
- API changes (new required parameters, removed endpoints).
- Database migrations or schema changes.
- Configuration format changes.
- Dependency version bumps with breaking changes.
Output Format
## Summary
- <1-3 bullet points describing the change>
## Changes
- <grouped description of modifications>
## Testing
- <what was tested and how to verify>
## Breaking Changes
- <list any breaking changes, or "None">
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 · 69 lines · 3 tokens per session scan A 302bdcdb3800
pr-description is a skill published in the GitHub repository PedroMosquera/squadai (8 stars, last pushed 1mo ago), licensed MIT. It adds 3 tokens to every session and 474 once invoked, about $0.0000 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
changelog
Update CHANGELOG.md with user-facing changes. Use when the user wants to update the changelog, prepare for a release, or document what changed since the last version.
commit
Write clear commit messages in conventional commits format. Use when the user is done with changes and wants to commit, says 'commit this', asks for a commit message, or has staged changes ready to go.
review
Self-review code before pushing. Use when the user wants to check their changes, asks 'anything I missed', says 'ready to push', or wants a pre-PR sanity check.
share-a-library
Use when a managed library is ready to publish to GitHub and hand to teammates as an install command. Run the GitHub publishing steps, then return the exact shareable install command.
gwm
Manage git worktrees across any repository with the gwm Rust binary (CLI + ratatui TUI). Use when the user asks to create / list / remove / bootstrap / switch / link worktrees, run a command across worktrees (gwm exec) or reclaim build artifacts (gwm clean), materialise a PR into a worktree (gwm review), drive a…
ijfw-preflight
Run the IJFW preflight pipeline (11 gates, fail-fast). Trigger: 'ijfw preflight', 'run preflight', 'check before ship', 'preflight gates', 'validate before release'.