AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Ship It

skill-paultyng-skill-issue-ship-it · by paultyng

End-to-end shipping workflow. Formats, lints, tests, creates a changelog entry, commits with conventional commits, pushes, updates PR description, and suggests reviewers. Use when the user says "ship it", "commit and push", "fmt lint test commit push", or similar shipping commands.

No reviews yet
0 installs
37 views
0.0% view→install

Install

$ agentstack add skill-paultyng-skill-issue-ship-it

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-paultyng-skill-issue-ship-it)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
2mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Ship It? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Ship It

Run the full pre-commit pipeline, commit, push, and handle PR housekeeping.

1. Verify

Run verification per [verify-when-complete](../verify-when-complete/SKILL.md). Stop if any step fails.

Review-status check (informational, non-blocking). If a .reviews//SUMMARY.md exists whose GIT_COMMIT_FULL metadata header matches the current HEAD SHA, count the rows under ## Findings — untracked and inside the ` block for Findings — tracked`, then print a single line:

Review status:  untracked /  tracked findings @  ()

Do not block on N > 0/ship-it runs because the user said so. The line is a sanity check, not a gate. If no matching SUMMARY.md exists, skip the line silently (don't run /review-all from here).

2. Changelog

Check if the project has a changelog convention:

  1. If Taskfile.yaml has a changelog task, run task changelog and follow its output.
  2. Otherwise, look for existing changelog entries:
  • Per-PR fragment directories like .changeset/ (JS/TS via @changesets/cli), .changes/ (Python via towncrier), or similar project-defined conventions
  • CHANGELOG.md at the repo root
  1. If a convention is found, create a terse entry following the existing format and patterns.
  2. If no changelog convention exists, skip this step.

3. Commit

Stage all changes and commit using Conventional Commits format:

[optional scope]: 

Common types: feat, fix, refactor, test, docs, chore, ci, build.

Always create a new commit. Never amend.

Apply terse-output commit-message tone: imperative subject ≤72 chars, body explains why (the diff shows what), no "this commit does X" / "I" / "we" / "now". Keep the Co-Authored-By: Claude… attribution.

4. Push and PR

Push the current branch:

git push -u origin HEAD

If a PR exists for the current branch, update its title and description to reflect the current state:

gh pr edit --title "" --body-file /tmp/pr-body.md

For PRs with diffs over ~20 files or ~500 lines, delegate body authoring to a subagent (model: sonnet per subagent-model-routing — PR-body authoring from a non-trivial diff requires real synthesis reasoning) per parallelize-subagents and subagent-prompt-contract: paste the commit list and git diff --stat inline, ask for a summary section + bullet list of notable changes capped at ~200 words, and have the subagent return with the four-state Status line. Main writes /tmp/pr-body.md from the summary. Small PRs stay inline.

If no PR exists, run [create-pr](../create-pr/SKILL.md) to open one.

5. Suggest Reviewers

If a PR exists, query reviewer state and present suggestions:

gh api graphql -f query='
{ repository(owner:"OWNER", name:"REPO") { pullRequest(number:NUM) {
  reviewRequests(first:10) { nodes { requestedReviewer { ... on User { login } ... on Team { slug } } } }
  latestReviews(first:10) { nodes { author { login } state } }
  suggestedReviewers { reviewer { login } isAuthor isCommenter }
} } }'

Logic:

  • If someone already reviewed, suggest re-requesting the same reviewer.
  • If a review is already requested, note who.
  • If no reviewer yet, present GitHub's suggestedReviewers list.
  • For deeper git-history-based suggestions, use /analyze-knowledge. It fans out per-area analysis to subagents for PRs with >20 files, so keep the parent context clean.
  • Do not auto-assign. Present suggestions and let the user decide.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.