np CLI
The CLI takes an npm package through checks, versioning and publication for a user-reviewed release prepared with an agent.
- 7,717 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- The CLI runs project scripts, changes versions and tags, publishes a package and pushes with user credentials.
Install
In your terminal, with SkillFoxx CLI
npx skillfoxx add cli/npDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The CLI runs project scripts, changes versions and tags, publishes a package and pushes with user credentials.
This is third-party code. Review the repository files before installing.
What it does
Before changing a version, np checks the branch and working tree, installs dependencies and runs tests. Users choose the release in an interactive wizard, then the tool prepares a commit and tag. An agent can inspect package contents and the release plan before upload. The CLI then publishes the package and pushes Git commits and tags. A successful release can open a GitHub Release draft. Dry-run mode displays tasks without executing them for preflight review.
Who it is for. npm package maintainers releasing a single project locally and reviewing the plan with an agent.
Good fit when
- A single npm package is ready for a coordinated release.
- Work finished on another branch, and the author prepares a switch to the release branch.
- A published version needs a GitHub release-description draft.
- Tests and a clean working tree should be checked before versioning.
Not a fit when
- You need a coordinated multi-package monorepo release.
- Package publishing or Git pushes are not authorized.
- The primary release workflow must run entirely in CI without a local interactive step.
Example request
Inspect package contents and prepare a dry-run patch-release plan with np without executing tasks or publishing.Limitations
Node.js 22, npm 10 and Git 2.11 or newer compatible versions are required. np does not support monorepos or release several packages in one operation. The tool is designed for local interactive use, and CI is not its intended primary environment. If a publish or postpublish hook fails after upload, the package may already be live; inspect the registry before retrying even when the command reports an error.
How to disable. Stop np and inspect the branch, tags, remote repository and package registry. Interruption does not guarantee that an already published version is undone.
FAQ
How do I see the plan without executing it?
Run np with `--dry-run`.
What opens without arguments?
An interactive version-selection and publishing workflow.
Can I open only the GitHub release form?
Yes. `np release-draft` opens it for the latest local tag without versioning or publishing.
Does cancellation restore a branch after switching?
No. Completed branch switches or updates remain.
Does a publishing error prove the package is absent?
Not always. Check the registry first if a late hook failed.
Discussion
No questions or reviews yet.
Related
CLI toolsrelease-it combines version changes, Git tags and package publishing in a configurable release workflow with a preview mode.
Nx CLI adopts npm, pnpm or yarn scripts, so teams introduce shared monorepo checks gradually while retaining their commands.
PM2 is a process manager that saves background app lists for restart after reboot and displays their status in the terminal.
GitHub Actions workflows run on your machine, and a failing step pauses so the agent can fix the file and retry it.
A local gate in front of git push: the branch goes through review, tests, docs and lint in a separate worktree before it reaches the remote with a PR
multi-gitter runs one script across multiple Git repositories and creates pull requests for the resulting file changes.
README in short
Release branch, registry and test script are configurable. Prereleases can use a separate distribution tag.