agentleFS
Sign inStart free
madebywildmadebywild/agent-harness/.claude/skills/npm-workflow-release/SKILL.md

npm-workflow-release

Skill16 starsChanged 7 months agoMITView on GitHub

Release agent-harness packages to npm and verify publication. Use when the user asks to cut a release, push a missing release tag, or troubleshoot why a version was not published.

  • Commits and pushes

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 8

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run the release workflow for this repository end-to-end.

    line 8
  2. Very specific:

    Use $ARGUMENTS as the target version when provided (for example: 1.6.0 or v1.6.0).

    line 10
  3. Very specific:

    If $ARGUMENTS is provided, normalize it to X.Y.Z and vX.Y.Z.

    line 15
  4. Distinctive:

    If not provided, infer the intended version from context and confirm package files match.

    line 16
  5. Very specific:

    Check packages/manifest-schema/package.json and packages/toolkit/package.json.

    line 18
  6. Very specific:

    Ensure both version values are identical and equal to the target version.

    line 19
  7. Very specific:

    Check .github/workflows/publish-npm.yml triggers on tag push (v*).

    line 21
  8. Very specific:

    Run GITHUB_REF_NAME=vX.Y.Z pnpm run release:guard before publishing.

    line 22
  9. Distinctive:

    Ensure the release tag exists remotely.

    line 23
  10. Very specific:

    Check local and remote tags for vX.Y.Z.

    line 24
  11. Distinctive:

    If missing on remote, push it: git push origin vX.Y.Z.

    line 25
  12. Distinctive:

    Verify npm publication for both packages.

    line 29
  13. Distinctive:

    If no workflow run appears, the tag was likely not pushed to remote.

    line 38
  14. Distinctive:

    If prepublish fails, fix version mismatch or tag mismatch first.

    line 39
  15. Very specific:

    If publish fails with auth errors, confirm NPM_TOKEN in GitHub Actions secrets.

    line 40
  16. Distinctive:

    If verify-published fails due lag, retry after npm propagation delay.

    line 41

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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

npm-workflow-release

Run the release workflow for this repository end-to-end.

Use $ARGUMENTS as the target version when provided (for example: 1.6.0 or v1.6.0).

Steps

  1. Resolve the target version.
    • If $ARGUMENTS is provided, normalize it to X.Y.Z and vX.Y.Z.
    • If not provided, infer the intended version from context and confirm package files match.
  2. Validate lockstep package versions.
    • Check packages/manifest-schema/package.json and packages/toolkit/package.json.
    • Ensure both version values are identical and equal to the target version.
  3. Confirm release workflow prerequisites.
    • Check .github/workflows/publish-npm.yml triggers on tag push (v*).
    • Run GITHUB_REF_NAME=vX.Y.Z pnpm run release:guard before publishing.
  4. Ensure the release tag exists remotely.
    • Check local and remote tags for vX.Y.Z.
    • If missing on remote, push it: git push origin vX.Y.Z.
  5. Monitor the publish run in GitHub Actions.
    • Use gh run list --workflow publish-npm.yml.
    • Watch the matching run with gh run watch <run-id> --exit-status.
  6. Verify npm publication for both packages.
    • npm view @madebywild/agent-harness-manifest dist-tags --json
    • npm view @madebywild/agent-harness-framework dist-tags --json
    • Confirm latest (or requested tag) points to X.Y.Z.
  7. Report outcome with concrete evidence.
    • Include tag push result, workflow run id/status, and npm verification output summary.

Troubleshooting

  • If no workflow run appears, the tag was likely not pushed to remote.
  • If prepublish fails, fix version mismatch or tag mismatch first.
  • If publish fails with auth errors, confirm NPM_TOKEN in GitHub Actions secrets.
  • If verify-published fails due lag, retry after npm propagation delay.

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