vltansky/ship-it
skills/ship-it/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add vltansky/skills ship-itInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 22, 2026, 1:46 AM196.6s2 files scanned
SKILL.md
- name:
- ship-it
- description:
- 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.
Create PR
Step 1: Check state
git branch --show-current && git status -s && git diff HEAD --stat
- Detect username:
git config user.nameor 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.
Related Skills
vltansky/hetzner-codex-remote
tools
VerifiedTrustedCommunity
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.
7SKILL.mdUpdated May 13, 2026
vltansky/what-i-did
data-ai
VerifiedTrustedCommunity
Summarize your GitHub activity from the last 24 hours across all repos. Use when user says "what did I do", "my activity", "standup", "recap", "summarize my day", "what-i-did", "git activity", "daily summary".
7SKILL.mdUpdated Apr 21, 2026
vltansky/tdd
development
VerifiedTrustedCommunity
Test-driven development loop. Write failing test first, then implement to make it pass. Use when the user says 'tdd', 'test first', 'write the test first', 'failing test', 'red green refactor', or for any bug fix where the fix should be proven by a test. Also use when autopilot or other skills need test-first execution.
7SKILL.mdUpdated Apr 21, 2026
vltansky/simplify
development
VerifiedTrustedCommunity
Review changed code for reuse, quality, and efficiency, then fix any issues found. Use when the user says "simplify", "simplify this", "review changes", "clean up my code", "check for duplicates", "code reuse review", or wants a post-change quality sweep.
7SKILL.mdUpdated Apr 21, 2026