ship-it
Create a GitHub PR with conventional format and AI session context. Use when user says 'create PR', 'open PR', 'submit changes', 'send to dev', 'ship it', or is done with their task.
Best use case
ship-it is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Create a GitHub PR with conventional format and AI session context. Use when user says 'create PR', 'open PR', 'submit changes', 'send to dev', 'ship it', or is done with their task.
Teams using ship-it should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/ship-it/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How ship-it Compares
| Feature / Agent | ship-it | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Create a GitHub PR with conventional format and AI session context. Use when user says 'create PR', 'open PR', 'submit changes', 'send to dev', 'ship it', or is done with their task.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Create PR ## Step 1: Check state ```bash git branch --show-current && git status -s && git diff HEAD --stat ``` - Detect username: `git config user.name` or extract from branch prefix - If on `master`/`main`/`prod`: create a feature branch: ```bash git checkout -b <username>/<feature-name> ``` Branch name from the diff context — short, descriptive, kebab-case. ## Step 2: Commit + Push If uncommitted changes exist: **If staged files exist** (respect user's selection): ```bash git commit -m "<msg>" && git push -u origin HEAD ``` **If no staged files** (stage everything): ```bash git add . && git commit -m "<msg>" && git push -u origin HEAD ``` Commit message: conventional format (`feat:`, `fix:`, `refactor:`, etc.), concise. ## Step 3: Generate AI Session Context Generate a privacy-safe summary for reviewers from the current conversation. You already have full context of: - What problem was discussed - What approaches were considered - What decisions were made and why - What trade-offs were evaluated Synthesize directly from your memory of this session. ### What to include vs exclude | Include | Exclude | |---------|---------| | Problem being solved | Exact user prompts | | Solution approach chosen | Mistakes/failed attempts | | Key decisions + WHY | Debugging struggles | | Trade-offs considered | Personal info/credentials | | Technical rationale | Anything embarrassing | ### Format as collapsible block ```markdown <details> <summary>AI Session Context</summary> **Problem:** [1 sentence - what was broken/needed] **Approach:** [1 sentence - solution strategy] **Key Decisions:** - [Decision]: [Rationale - the WHY] - [Decision]: [Rationale - the WHY] **Trade-offs Considered:** - [Option A vs B]: Chose A because [reason] </details> ``` ### Skip Conditions Skip AI Session Context if: - Trivial change (typo, version bump, config) - No meaningful decisions were made - User says "no context" or "skip context" ## Step 4: Create PR **Format:** ``` <feature_area>: <Title> (80 chars max) <TLDR> (1-2 sentences) - bullet 1 - bullet 2 <details> <summary>AI Session Context</summary> ... </details> ``` ```bash gh pr create --title "<title>" --body "<body>" ``` Display the returned PR URL on its own line so it's clickable.
Related Skills
roast-my-code
Brutally honest code review with comedic flair. Roasts the sins, then redeems the sinner. Use when the user says "roast my code", "roast this", "tear this apart", "be brutal", "savage review", "destroy my code", "flame this", or wants entertaining but actionable code feedback. Also triggers on "what's wrong with this code" with a casual tone, "how bad is this", or "rate my code".
roast-my-agents-md
Brutally honest AGENTS.md/CLAUDE.md review backed by real A/B test evidence. Not just opinions — actual proof that your rules are dead weight. Roasts instruction files for bloat, slop, and redundancy, then proves it by running evals. Use when user says "roast my agents.md", "roast my CLAUDE.md", "prove my rules are useless", "eval roast", or wants entertaining evidence-based feedback on their AI config files. Also triggers on "audit my instructions" or "are my rules helping".
rfc-research
Research a technical topic and produce an RFC document backed by real code evidence from GitHub. Use when user says 'write an RFC', 'RFC research', 'create RFC for', 'technical proposal', 'design doc', 'investigate X', 'research X and write a proposal', 'architecture decision record', 'ADR', or needs a structured technical decision document with prior art analysis.
retro
Weekly engineering retrospective. Analyzes commit history, work patterns, and code quality metrics with persistent trend tracking. Team-aware: per-person contributions with praise and growth areas. Use when asked to 'weekly retro', 'what did we ship', 'engineering retrospective', 'how was this week', or 'show me the commit stats'. Proactively suggest at the end of a work week or sprint.
hetzner-codex-remote
Prepare a Hetzner Cloud VPS for secure Codex remote SSH access. Use when the user wants to create or configure a Hetzner server for Codex remote control, fix "No codex found in PATH" on a remote machine, install agent development tooling on a VPS, harden SSH access to a Hetzner server, or connect the server through Codex Settings, Connections, Add SSH.
grill-me
Structured adversarial review that pushes back on a plan, challenges the premise, compares alternatives, and stress-tests the design until the main risks are explicit. Use when the user asks to "grill me", stress-test a plan, poke holes in an approach, challenge assumptions, pressure-test a design, or validate an early-stage idea before building ("I have an idea", "is this worth building", "grill me on this idea").
fix-pr-comments
Handle feedback from PR reviewers. For each inline thread: reply on-thread and resolve after user approves. Use when developers left comments on your PR and you need to address them. Triggers on 'address comments', 'fix PR feedback', 'what did the reviewer say', 'handle review', 'resolve comments', 'comments from dev', 'dev feedback'.
design-review
Designer's eye visual audit of a live site — finds typography issues, spacing violations, AI slop patterns, hierarchy problems, interaction state gaps — then fixes them with atomic commits and before/after screenshots. Use when asked to 'audit the design', 'visual QA', 'design polish', 'does this look good', 'check the UI', or 'fix the design'. Proactively suggest when the user mentions visual inconsistencies or wants to polish a live site before shipping.
debug
Systematic root-cause debugging for any bug — backend, frontend, logic, integration. Hypothesis-driven investigation with evidence collection. Use when the user says 'debug', 'investigate', 'why is this broken', 'root cause', 'trace this bug', 'figure out why', 'this doesn't work', or 'unexpected behavior'. For frontend-specific runtime debugging with a log server, use /debug-mode instead.
debug-mode
This skill should be used when debugging frontend/UI bugs that need runtime evidence. USE THIS SKILL (instead of adding console.log) when you're about to say "add console.log and ask user to check", "open DevTools and tell me what you see", "reproduce the bug and share the output", "check the browser console". Triggers: "debug this", "fix this bug", "why isn't this working", "investigate this issue", "trace the problem", "figure out why X happens", "UI not updating", "state is wrong", "value is null/undefined", "click doesn't work", "modal not showing". Automates log collection server-side - you read logs directly, no user copy-paste needed.
chat-history
Search previous AI chat conversations from Cursor IDE and Claude Code by content, affected file, or project. Use when the user asks about previous conversations, wants to find how they solved something before, or needs to recall past AI interactions.
batch
Parallel work orchestration — decompose large changes into 5-30 worktree agents that each open a PR. Use when the user says 'batch', 'do this in parallel', 'split into PRs', 'bulk change', 'mass refactor', or wants a sweeping mechanical change across many files.