li3p/ship
skills/ship/SKILL.md
Validate a branch and draft a pull request description from real commits and diffs. Use when preparing a PR, checking branch readiness, or writing reviewer-facing release context.
testing
Updated Apr 23, 2026
$ install --global
skillsauthnpx skillsauth add li3p/skills shipInstall 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 23, 2026, 11:10 PM16.8s1 file scanned
SKILL.md
- name:
- ship
- description:
- Validate a branch and draft a pull request description from real commits and diffs. Use when preparing a PR, checking branch readiness, or writing reviewer-facing release context.
Ship
Prepare the current branch for pull request review.
Workflow
- Identify the base branch, current branch, commits ahead, and diff size.
- Run the relevant test suite before drafting the PR when the command is clear. If tests fail, stop and report the failures first.
- Inspect the actual diff, not only commit messages.
- Flag branch hygiene issues:
- very large diff
- too many commits for review
- generated files mixed with source changes
- missing tests for behavior changes
- debug artifacts or obvious preflight blockers
- Draft the PR description.
PR Description
Use this structure:
## Summary
## Changes
## How to Test
## Risk Assessment
## Related Issues
Write for a reviewer who has not watched the implementation happen. Be specific about user-visible behavior, data changes, public API changes, migrations, performance-sensitive paths, rollout risks, and verification steps.
Do not create the pull request unless the user explicitly asks.
Related Skills
li3p/notion-search
documentation
VerifiedTrustedCommunity
Search Notion for pages or databases by query using marknotion. Use when the user references a Notion page by name rather than URL, when locating a page to publish to or pull from, or when discovering what trackers and docs exist in the connected workspace.
SKILL.mdUpdated May 27, 2026
li3p/notion-pull
documentation
VerifiedTrustedCommunity
Export a Notion page to local Markdown using marknotion. Use when the user wants to pull a spec, design doc, meeting notes, or any Notion page into the repository as a Markdown file, or wants to read Notion content as context for a task.
SKILL.mdUpdated May 27, 2026
li3p/notion-publish
documentation
VerifiedTrustedCommunity
Publish a local Markdown file to a Notion page using marknotion. Use when the user wants to push README, docs, changelogs, or any Markdown content to Notion, either updating an existing page or creating a new one under a parent page.
SKILL.mdUpdated May 27, 2026
li3p/testmatch
testing
VerifiedTrustedCommunity
Generate tests that match an existing project's testing style. Use when adding coverage for a target file, function, bug fix, or edge case while preserving local conventions.
SKILL.mdUpdated Apr 23, 2026