publish-repo

Automates end-to-end npm package releases including version bumps, docs, tests, publishing, and GitHub Releases.

Updated May 22, 2026
One-click install
npx skills add https://github.com/kitfunso/claude-config --skill publish-repo-kitfunso
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: publish-repo
Source: https://github.com/kitfunso/claude-config/tree/main/skills/publish-repo
Command: npx skills add https://github.com/kitfunso/claude-config --skill publish-repo-kitfunso

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Shipping an npm release involves many error-prone manual steps: bumping versions across multiple manifests, updating changelogs and READMEs, running builds and tests, publishing to npm, tagging, pushing, and creating GitHub Releases. This Skill orchestrates the entire workflow so nothing gets missed. ## Core Features & Use Cases - Multi-manifest version bumping: Searches the repo for every version string (package.json, plugin manifests, nested packages) and updates them all, avoiding the pitfalls of npm version. - Documentation enforcement: Mandates CHANGELOG entries, README "What's new" sections, and post-publish doc audits so release notes always match what shipped. - Full release pipeline: Runs build, tests, commit, npm publish, git tag/push, GitHub Release creation via gh, and global CLI install verification. - Use Case: After merging a new feature, ask the AI to ship the package. It infers a minor bump, updates all manifests and docs, runs the test suite, publishes to npm, pushes the tag, and creates a GitHub Release with extracted changelog notes. ## Quick Start Ship this package as a new release with a minor version bump.

Frequently Asked Questions about publish-repo

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I publish an npm package with version bump and changelog?▼

Bump the version in every manifest manually (never use npm version, which misses nested files), add a CHANGELOG entry, run build and tests, commit, then run npm publish followed by git tag and push. This Skill automates that exact sequence.

Why should I avoid npm version when bumping package versions?▼

npm version only updates package.json and package-lock.json, leaving nested package.json files, plugin manifests, and version strings in source code stale. Manual edits with a repo-wide grep for the old version ensure every manifest stays in sync.

How do I create a GitHub Release from a CHANGELOG entry?▼

Extract the new version's CHANGELOG section with awk into a notes file, then run gh release create with the tag, a one-line headline title, and --notes-file pointing to the extracted notes. Use --latest only for the newest stable release.

What happens if npm publish fails during a release?▼

The workflow stops and reports the failure, whether from authentication issues or a version conflict. The commit and version bumps remain local, so you can fix the issue and retry publishing without amending previous commits.

Does this release workflow work for CLI tools?▼

Yes. If package.json has a bin field, the workflow installs the published version globally with npm install -g and verifies it by running the CLI's --version command after publishing.