Borrowing it
Nothing to install: this file belongs to shift-editor/shift. 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/shift-editor/shift/main/.agents/skills/pr/SKILL.mdgit clone --depth 1 https://github.com/shift-editor/shiftWrote 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/shift-editor/shift/pr)<a href="https://agentmods.dev/skills/shift-editor/shift/pr"><img src="https://agentmods.dev/badge/skills/shift-editor/shift/pr/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/shift-editor/shift/pr"><img src="https://agentmods.dev/badge/skills/shift-editor/shift/pr.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.00058 | $0.01952 |
| Opus 5.5 | $0.00023 | $0.00781 |
| Sonnet 5.5 | $0.00012 | $0.00390 |
| Haiku 4.5 | $0.00006 | $0.00195 |
Grade A, and why
pr 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 3d 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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/pr — How Shift pull requests are written
A pull request is one reviewable product or engineering change. Its title must make sense in history and as potential Release Please input.
Title syntax
Every pull request title uses Conventional Commits:
<type>[optional scope][optional !]: <concise imperative description>
Use the same types and subject rules as /commit. Examples:
feat: add source conversion preview
fix(document): preserve the last valid save
ci: publish signed Alpha artifacts
The title must:
- be at most 72 characters;
- use lowercase imperative wording after the colon;
- describe the user or system outcome, not the list of files changed;
- omit trailing punctuation, emoji, agent labels, and
[codex]prefixes.
CI rejects titles that are not Conventional Commits. GitHub may also use the pull request title as a squash commit subject, so treat it as release-quality history.
Release Please behavior
Release Please reads conventional commits merged to main and maintains a draft release pull request.
feat,fix, andperfbecome public changelog entries.refactor,test,docs,build,ci,style, andchoreremain valid but are hidden from public release notes.- Ordinary pull requests must not bump the product version or edit generated changelog sections.
- Maturity and milestone changes require explicit user approval and a
Release-As:footer. - The generated
chore: release Shift …pull request is special: review its version, changelog, warning text, and artifact readiness before merging it.
Pull request body
Use a concise body with evidence:
## Summary
- what changed and why
- important behavioral or architectural boundary
## Issue
Closes #123
## Testing
- `exact command`
- focused manual verification
Add ## Risks or ## Follow-up only when they materially help review. Do not add empty sections, generic claims such as “tests pass,” generated marketing prose, or agent attribution.
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.
- 3d ago Changed · +11 lines 150b2fde5ebf
- 1mo ago First seen · 148 lines · 58 tokens per session scan A 999e84a13789
pr is a skill published in the GitHub repository shift-editor/shift (379 stars, last pushed today), licensed Apache-2.0. It adds 58 tokens to every session and 1,952 once invoked, about $0.0002 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-09-01.
Other skills, from other repositories
pn-github-vertical-slices
Break a plan or PRD into tracer-bullet vertical slices and create GitHub Issues via GitHub MCP (official github/github-mcp-server). Dependencies first (AFK/HITL). Use after pn-writing-plans or pn-create-prd when work must ship as Issues.
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
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.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.
gait-session-tracking
GAIT session lifecycle management - branch creation, turn recording, audit logging for every NetClaw operation. Use when starting a new NetClaw session, recording a health check or config change, pinning a pre-change baseline, or viewing the audit trail for a troubleshooting session.