Skills

vs-ship-it

Installation
SKILL.md

Create PR

Step 0: Ensure review ran

Before shipping, check if roast-my-code was already run in this session.

If not run yet: run it now. Wait for both passes to complete (Pass 1 auto-fixes, Pass 2 presents sins — auto-select option b for critical + serious). Apply fixes before proceeding.

If already run: continue to Step 1.

Step 1: Check state

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:
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):

git commit -m "<msg>" && git push -u origin HEAD

If no staged files (stage everything):

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

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

gh pr create --title "<title>" --body "<body>"

Display the returned PR URL on its own line so it's clickable.

Step 5: Watch CI

Block until CI checks complete. This keeps the agent in context so it can fix failures immediately without the user having to start a new session and re-explain the change.

gh pr checks --watch --fail-fast

If checks pass: "CI green. Ready for review."

If checks fail:

  1. Read the failure: gh pr checks --json name,state,description --jq '.[] | select(.state == "FAILURE")'
  2. Get logs: gh run view <run-id> --log-failed | tail -50
  3. Fix the issue, commit, push.
  4. Watch again: gh pr checks --watch --fail-fast
  5. Max 2 fix attempts. If still failing after 2: report what's broken, stop.

Tip: while this agent watches CI, the user can open a new terminal and start a separate claude session to keep working on something else in parallel.

Workflow

Prev: /vs-roast-my-code (review passed) | /vs-autopilot (handoff suggests ship-it) Next: /vs-fix-pr (address reviewer feedback) | done

Related skills

More from vltansky/vladstack

Installs
1
Repository
vltansky/vladstack
GitHub Stars
1
First Seen
Apr 1, 2026