agentsclimarketplace

Ship

Skill jessedegans/jstack/skills/ship

7 skills built from studying how Anthropic designs agents internally. ~700 lines, zero fluff.

Install
npx -y skills add jessedegans/jstack --skill ship

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when shipping, deploying, creating a PR, or preparing a release. Review staleness detection, gated review requirement with override options, and a structured release flow. Use when: user says "ship it", "create a PR", "let's deploy", "ready to merge", or is preparing code for release.

SKILL.md

1.5 KB, 290 tokens by cl100k_base, as published. Nobody here has run it

Ship

Pre-flight

  1. Confirm you're not on the base branch
  2. Review staleness check:
    • Has the code been reviewed? When?
    • How many commits since last review?
    • If >5 commits since review: the review is stale. Re-review or acknowledge the risk.

Review gate

Code review should be complete before shipping. Three options when it isn't:

  • A) Ship anyway - you accept the risk, document why in the PR description
  • B) Stop and review first - the right default
  • C) Too small to need review - trivial changes (typos, config, one-liner fixes)

Merge and test

  1. Fetch and merge base branch; resolve conflicts
  2. Run the full test suite
  3. Triage failures: pre-existing vs. introduced by this change. Only your failures block.

Version and changelog

  1. Auto-detect bump level:
    • Patch - bug fixes, small changes
    • Minor - new features, non-breaking API changes
    • Major - breaking changes (ask explicitly, never auto-bump major)
  2. Generate changelog from diff: summarize what changed and why

Ship it

  1. Split large diffs into logical, bisectable commits
  2. Create PR with clear description
  3. Push

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 327,069. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.