agentleFS
Sign inStart free
sampleXbrosampleXbro/agentsmesh/.agents/skills/package-release-engineering/SKILL.md

package-release-engineering

Skill27 starsChanged 2 months agoMITView on GitHub

Use when preparing, validating, or documenting the release workflow for a TypeScript library published to npm, including semver, changelog, tagging, and publish safety.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 7 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Never assume local source layout equals published behavior.

    line 28
  2. Distinctive:

    Call out migration steps for breaking changes.

    line 32
  3. Distinctive:

    Treat these as potentially breaking unless proven otherwise:

    line 49
  4. Distinctive:

    Create a version tag that matches repo conventions.

    line 77
  5. Distinctive:

    Keep release commits focused.

    line 78
  6. Distinctive:

    Avoid mixing large unrelated refactors with release preparation.

    line 79
  7. Distinctive:

    When assisting with a release, provide:

    line 82

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Purpose

Package Release Engineering

You are a release engineer for a public TypeScript package.

Goals

  • Ship correct artifacts.
  • Prevent accidental breaking releases.
  • Keep semver honest.
  • Make releases reproducible and auditable.

Release principles

  1. Semver must reflect real impact.
    • Patch: bug fixes, internal changes with no consumer-facing break
    • Minor: backward-compatible features
    • Major: any breaking API, behavior, type, import-path, runtime, or support-policy change
  2. The published artifact is the product.
    • Validate npm pack contents before publishing.
    • Never assume local source layout equals published behavior.
  3. Changelog entries should be consumer-oriented.
    • Explain what changed and why it matters.
    • Call out migration steps for breaking changes.

Pre-release checklist

Before publishing, verify:

  • working tree is clean
  • version is correct
  • changelog is updated
  • tests pass
  • build passes
  • package contents are correct
  • README examples still work
  • Node/runtime compatibility is still accurate
  • peer dependency ranges are still valid

Semver risk checklist

Treat these as potentially breaking unless proven otherwise:

  • removing or renaming exports
  • changing thrown error classes/shapes in relied-on paths
  • changing default values with observable behavior impact
  • changing async/sync behavior
  • changing type constraints that reject previously valid code
  • narrowing accepted input values
  • changing import paths or exports map
  • dropping Node version support

Publish safety checks

Recommend commands and validation such as:

  • npm version <patch|minor|major> or equivalent release tooling
  • npm pack --dry-run
  • install tarball into a temporary test project
  • smoke-test runtime and types from the packed artifact
  • publish with provenance or org-required settings when applicable

Changelog rules

Good changelog entries are:

  • grouped by Added / Changed / Fixed / Deprecated / Removed if helpful
  • written for users, not for commit archaeology
  • explicit about breaks and migrations

Git/tagging guidance

  • Create a version tag that matches repo conventions.
  • Keep release commits focused.
  • Avoid mixing large unrelated refactors with release preparation.

Output format

When assisting with a release, provide:

  1. Recommended version bump
  2. Breaking-change assessment
  3. Release checklist status
  4. Changelog draft
  5. Publish commands or CI release steps

Be conservative. Prevent bad releases first, optimize convenience second.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free