Borrowing it
Nothing to install: this file belongs to ArcBlock/agent-skills. 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/ArcBlock/agent-skills/main/.claude/skills/pull-request/SKILL.mdgit clone --depth 1 https://github.com/ArcBlock/agent-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/arcblock/agent-skills/pull-request)<a href="https://agentmods.dev/skills/arcblock/agent-skills/pull-request"><img src="https://agentmods.dev/badge/skills/arcblock/agent-skills/pull-request/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/arcblock/agent-skills/pull-request"><img src="https://agentmods.dev/badge/skills/arcblock/agent-skills/pull-request.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.00023 | $0.02690 |
| Opus 5.5 | $0.00009 | $0.01076 |
| Sonnet 5.5 | $0.00005 | $0.00538 |
| Haiku 4.5 | $0.00002 | $0.00269 |
Grade A, and why
pull-request 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 1mo 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 — 385 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pull Request Skill
Generate standardized Pull Requests by analyzing the diff between current branch and main branch.
Step 0: Check for Project PR Template (IMPORTANT)
CRITICAL: Before generating PR content, ALWAYS check if the project has a custom PR template:
# Check for PR template in common locations
ls -la .github/PULL_REQUEST_TEMPLATE.md 2>/dev/null || \
ls -la .github/PULL_REQUEST_TEMPLATE/ 2>/dev/null || \
ls -la docs/PULL_REQUEST_TEMPLATE.md 2>/dev/null
If a PR template exists:
- Read the template file using the Read tool
- Use that template's structure for the PR body
- Fill in each section according to the template's format and comments
- Keep any checkboxes or structured lists from the template
If no PR template exists: Use the default template defined below.
PR Template (Default - Use only if no project template exists)
Based on analysis of high-quality PRs, use this template:
Title Format
<type>(<scope>): <description>
Types (same as Conventional Commits):
| Type | Description |
|---|---|
feat |
New feature |
fix |
Bug fix |
docs |
Documentation only |
style |
Code style changes |
refactor |
Code refactoring |
perf |
Performance improvement |
test |
Add or modify tests |
chore |
Build process or tools |
ci |
CI/CD configuration |
build |
Build system changes |
Scope: Optional, indicates affected module (e.g., agentloop, blocklet, auth)
Description:
- Imperative mood ("add" not "added")
- Lowercase first letter
- No period at end
- Under 72 characters
Body Format
## Summary
<1-5 bullet points describing key changes>
## Motivation / Context
<Why this change is needed - the problem being solved>
## Changes
<Detailed list of what was changed, organized by area>
## Test Plan
<How to verify the changes work correctly>
- [ ] Step 1
- [ ] Step 2
---
Generated with [Claude Code](https://claude.com/claude-code)
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.
- 1mo ago First seen · 385 lines · 23 tokens per session scan A a188cc706677
pull-request is a skill published in the GitHub repository ArcBlock/agent-skills (5 stars, last pushed 9d ago), licensed MIT. It adds 23 tokens to every session and 2,690 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-08-31.
Other skills, from other repositories
review-implement-phase
Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.
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.
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.
otto-pr-review-loop
Run Polly and OCR on a PR until all findings settle.
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.
verify-behavior
Verify or reproduce visible product behavior by driving the real UI with pi-computer-use's checked tools, requiring verified expect postconditions and durable state evidence for meaningful UI flows. Use when triage needs visual reproduction, implementation needs behavioral proof, review needs interactive confirmation…