bostonaholic/team-ship
skills/team-ship/SKILL.md
Commit, create PR, and ship the implementation after verification passes. Trigger on "ship it", "create the PR", or "/team-ship".
tools
Updated Apr 16, 2026
$ install --global
skillsauthnpx skillsauth add bostonaholic/team team-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 16, 2026, 2:38 PM4.2s1 file scanned
SKILL.md
- name:
- team-ship
- description:
- Commit, create PR, and ship the implementation after verification passes. Trigger on "ship it", "create the PR", or "/team-ship".
TEAM Ship — Standalone Phase
Run the SHIP phase. Requires verification.passed in the event log.
Execution
- Read
~/.team/<topic>/events.jsonl. Scan forverification.passed. - If not found: report "Verification not passed. Run /team-verify first." and stop.
- Extract beads ID from the first event in the log (
feature.requestedorbug.reported). Checkdata.beadsId. If present, this pipeline is tracking a beads issue. - Update CHANGELOG.md before committing (see Changelog Update below).
- Present shipping options:
- Commit + PR — branch, commit, open pull request
- Commit locally — commit to current branch
- Keep as-is — leave changes uncommitted
- Execute user's choice.
- Close beads issue. If
beadsIdwas found in step 3 and the user chose to commit (either option), use/beads:close <beadsId>to mark the issue as done. Skip this if the user chose "keep as-is". - Append
feature.shippedevent to the log. - Delete
~/.team/<topic>/directory.
Changelog Update
Before creating the ship commit, update CHANGELOG.md following the changelog
methodology in skills/changelog/SKILL.md:
- Scan commits since the last changelog entry using
git log. - Filter to user-facing commits:
feat:,fix:,perf:,security:, and anyBREAKING CHANGE:footer. Excludechore:,test:,refactor:,ci:, anddocs:commits. - Translate each included commit to a plain-language user-facing bullet.
- Add entries under the
[Unreleased]section inCHANGELOG.md. Create the file with the Keep a Changelog header if it does not exist. - Include the
CHANGELOG.mdchange in the ship commit.
If there are no user-facing commits to document (all changes are internal), skip the changelog update and note this in the completion report.
Commit Discipline
When creating the commit, apply the git-commit methodology from
skills/git-commit/SKILL.md:
- Use Conventional Commits format:
feat:,fix:,refactor:, etc. - Subject line: 50 characters or fewer, imperative mood, no trailing period
- Body: wrapped at 72 characters, explains why not what
- One logical change per commit — the feature as a whole, not its implementation steps
- Reference the issue or plan in the footer if one exists
The ship commit represents the complete, user-visible feature. Write the subject to describe what the feature does for users, not how it was built.
Completion
Report the outcome (PR URL, commit hash, or "kept uncommitted").
Related Skills
bostonaholic/progress-tracking
data-ai
VerifiedTrustedCommunity
Todo-first progress convention for multi-step procedures — loaded by every multi-step agent to track its own steps without drift
3SKILL.mdUpdated Jun 2, 2026
bostonaholic/eng-design-doc-review
testing
VerifiedTrustedCommunity
Adversarially review a technical design document with fresh context before the human gate. Dispatches the built-in `general-purpose` subagent (clean context, no shared history with the design-author) against `docs/plans/<id>/design.md` and presents its verdict — APPROVE, REQUEST CHANGES, or COMMENT. Optional, not part of the QRSPI pipeline. Trigger on "review the design doc", "audit design.md", "is this design ready", or `/eng-design-doc-review`.
3SKILL.mdUpdated May 23, 2026
bostonaholic/code-review
development
VerifiedTrustedCommunity
Generator-evaluator separation and review methodology — loaded by review agents to enforce fresh-context review discipline, Conventional Comments format, and gate verdicts
3SKILL.mdUpdated May 2, 2026
bostonaholic/team-worktree
data-ai
VerifiedTrustedCommunity
Prepare one or more isolated git worktrees — one per repository the topic touches. Router action — no agent. Trigger on "set up the worktree", "isolate this work", or "/team-worktree".
3SKILL.mdUpdated Apr 23, 2026