agentdeck: Skill for Claude Code

.claude/skills/ship-pr/SKILL.md

ship-pr is a skill for Claude Code from agentdecksdk/agentdeck. It costs 0 tokens per session (1,784 once invoked), scanned A, original, MIT.

A five-stage workflow for turning a GitHub issue into a pull request, including understanding the request, designing the change, coding, reviewing, and checking it before merge.

In plain words
What is it for?
Use it when implementing an agentdeck issue as deck-dev. It guides the pull request description, implementation, self-review, checks, and readiness for merging.
Why use it?
It prevents code from being written before the requested change is understood and designed. It also prompts the developer to check paths that tests may not cover.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is agentdecksdk/agentdeck's own configuration. It tells Claude Code how to work on agentdeck itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything agentdeck configures →

Reuse

Borrowing it

Nothing to install: this file belongs to agentdecksdk/agentdeck. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/agentdecksdk/agentdeck/dev/.claude/skills/ship-pr/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/agentdecksdk/agentdeck

Made for: Claude Code.

Wrote 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.

agentmods badge for ship-pr

README.md
[![agentmods](https://agentmods.dev/badge/skills/agentdecksdk/agentdeck/ship-pr/github.svg)](https://agentmods.dev/skills/agentdecksdk/agentdeck/ship-pr)
Your own site
<a href="https://agentmods.dev/skills/agentdecksdk/agentdeck/ship-pr"><img src="https://agentmods.dev/badge/skills/agentdecksdk/agentdeck/ship-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.

agentmods 80×15 button for ship-pr

Your own site · 80×15
<a href="https://agentmods.dev/skills/agentdecksdk/agentdeck/ship-pr"><img src="https://agentmods.dev/badge/skills/agentdecksdk/agentdeck/ship-pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,784 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.01784
Opus 5.5 $0.00000 $0.00714
Sonnet 5.5 $0.00000 $0.00357
Haiku 4.5 $0.00000 $0.00178

Measured 1mo ago against content hash 65e6fb38d5f2, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

ship-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 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.

.claude/skills/ship-pr/SKILL.md · 142 lines

How it starts

The opening of the file, as written. The whole thing — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Ship a PR

Design the diff before writing it. The design binds nothing by itself, so Stage 1 stops and waits for the orchestrator to check it against the brief before Stage 2 touches source. Self-review is a checklist, not reflection: an unanswered question fails the stage, same as an unrun command.

Checklist

Copy this into your own response and check off each stage as you complete it:

Ship progress:
- [ ] 0. Understand: spec gate, engineering docs, seed the worktree
- [ ] 1. Design: PR body sections, then stop and wait for the design gate
- [ ] 2. Implement: match the analog, stay in budget (references/implement.md)
- [ ] 3. Self-review: the standard, ten shape questions, the coverage question (references/self-review.md)
- [ ] 4. Gate: make check green, gh pr ready

Freedom per stage

Thinking is high freedom. Verification and output are low: a checklist or a template you improvise is not one.

stage freedom why
0 Understand LOW on the spec gate, HIGH on reading the gate is binary: Done when and scope bounds present, or stop and comment
1 Design LOW on format, HIGH on content CI parses the budget block; what argument goes in it is judgment
2 Implement HIGH open field. Over-specifying here does real damage, and the issue this skill ships from puts it out of scope
3 Self-review LOW a checklist you can improvise is not a checklist
4 Gate LOW exact commands, fragile sequence

Register

Every instruction below, and in references/, carries exactly one of these:

register wording carries
CONSTRAINT MUST / NEVER what breaks if violated, named alongside it
EXPECTATION "the reviewer checks X" which finding class the miss earns
JUDGMENT "default is X, deviate when Y" nothing; your call

A CONSTRAINT without a stated consequence is a preference, not a CONSTRAINT: rewrite it or demote it.

Stages

stage freedom / register does writes
0. Understand LOW / CONSTRAINT on the gate Read the issue as spec. Spec gate below. Seed the worktree. nothing, or a gate comment
1. Design LOW / CONSTRAINT on format PR body sections, then stop. references/design.md draft PR, then wait
2. Implement HIGH / JUDGMENT Match the analog, stay in budget, test what the change exposes. references/implement.md source, tests, CHANGELOG
3. Self-review LOW / CONSTRAINT The standard (major features), ten shape questions, the coverage question, answered in writing. references/self-review.md the answers, visible in your response
4. Gate LOW / CONSTRAINT make check green, compact the body, gh pr ready. Below. ready PR

Read the full file on GitHub · 142 lines

Files

What ships with it

3 files 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.

Changes

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.

  1. 1mo ago Changed · +1 lines 65e6fb38d5f2
  2. 1mo ago Changed · +4 lines 7dc68592a4a9
  3. 2mo ago First seen · 137 lines · 0 tokens per session scan A ef2bb978d60d

Subscribe to this mod's changes

ship-pr is a skill published in the GitHub repository agentdecksdk/agentdeck (4 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,784 tokens. 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.

Related

Other skills, from other repositories

pr-triage-and-summary

Turn a change set into a concise implementation and risk summary.

ldilov/harness-forge · 19 tokens

github-pr-workflow

Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.

paperclipai/paperclip · 39 tokens

github-automation

GitHub workflow automation, PR management, issue tracking, and code review coordination. Integrates with GitHub Actions and repository management. Use when: PR creation, code review, issue management, release automation, workflow setup. Skip when: local-only changes, non-GitHub repositories.

ruvnet/ruflo · 61 tokens

agent-framework-py-release

Use when cutting a Python release for the microsoft/agent-framework monorepo. Triggers on "bump py versions", "cut a python release", "prepare release PR for python", "release py packages", "bump python to X.Y.Z", or similar requests to bump Python package versions and prepare a release PR. Handles all four lifecycle…

microsoft/agent-framework · 102 tokens

gh-issues

Fetch GitHub issues, spawn sub-agents to implement fixes and open PRs, then monitor and address PR review comments. Usage: /gh-issues [owner/repo] [--label bug] [--limit 5] [--milestone v1.0] [--assignee @me] [--fork user/repo] [--watch] [--interval 5] [--reviews-only] [--cron] [--dry-run] [--model glm-5]…

spinabot/brigade · 116 tokens

github

GitHub operations via gh CLI: issues, PRs, CI runs, code review, API queries. Use when: (1) checking PR status or CI, (2) creating/commenting on issues, (3) listing/filtering PRs or issues, (4) viewing run logs. NOT for: complex web UI interactions requiring manual browser flows (use browser tooling when available)…

spinabot/brigade · 101 tokens