Skills npm-release

📦

npm-release

Name: npm-release
Author: Dimon94

v1.1.0 Content revision r2 High Risk 📁 Filesystem access⚙️ External commands🌐 Network access

Publish cc-devflow Releases Safely

Manual npm releases can leave package files, tags, Git history, and registry versions inconsistent. This skill coordinates validation, versioning, changelog updates, publishing, rollback, and post-release checks.

Supports: Claude Codex Code(CC)

⚠️ 38 Poor

Stop for confirmation before installing.

Review the plan and obtain explicit user consent before changing files.

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "npm-release" from https://skillstore.io/skills/dimon94-npm-release.md and its manifest at https://skillstore.io/api/skills/dimon94-npm-release/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/dimon94-npm-release.md Signed manifest GET /api/skills/dimon94-npm-release/manifest Signed lockfile GET /api/skills/dimon94-npm-release/lockfile

Test it

Using "npm-release". Prepare a patch release, but do not push or publish.

Expected outcome:

Release preparation completed for version 1.1.1. Package files and changelog agree, verification passed, and the local commit and tag await approval.

Using "npm-release". Check whether version 1.2.0 was published consistently.

Expected outcome:

Registry verification passed. The package files, changelog, release commit, annotated tag, and npm registry all report version 1.2.0.

Using "npm-release". The npm publish step failed after the tag was pushed.

Expected outcome:

Publication is incomplete. Keep the existing commit and tag, record the registry error, verify authentication, and request approval before retrying publication.

Security Audit

High Risk

v9 • 7/23/2026 Open versioned report

Most static findings are false positives caused by Markdown formatting, fixed documentation references, authentication checks, and multilingual prose. The workflow does direct agents to run state-changing Git and npm commands, including publishing and destructive rollback, so explicit per-action approval is required. No prompt injection or obfuscated payload was found.

Files scanned

636

Lines analyzed

Review items

False positives ignored

Confirmed security concerns (1)

High

SKILL.md:120-128 SKILL.md:136-143

High-impact release actions lack immediate confirmation gates

The workflow groups remote pushes and npm publication into one command block, then provides unpublish and remote tag deletion commands without explicit per-action approval.

The commands and their state-changing effects are explicit, while neither block contains a direct confirmation step immediately before execution.

Capability review items (6)

These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.

High

SKILL.md:122-129

Ruby/shell backtick execution

```bash

The block pushes a branch and tag, publishes to npm, and executes the published package with npx. These authenticated network actions have material release and code-execution impact.

High

SKILL.md:138-143

Ruby/shell backtick execution

```bash

The fenced rollback block can unpublish a package, delete a local and remote tag, and revert a commit. These are destructive release operations.

Medium

SKILL.md:59-61

Ruby/shell backtick execution

```bash

The fenced block runs npm version, which modifies package.json and package-lock.json. The arguments are constrained, but the command changes release state.

Medium

SKILL.md:65-68

Ruby/shell backtick execution

```bash

The block runs a repository npm script and npm pack. Repository scripts and package lifecycle hooks execute local code, so the release source must be trusted.

Medium

SKILL.md:72-96

Ruby/shell backtick execution

```bash

The fenced block stages release files and creates a Git commit. These commands intentionally modify repository state, although their file arguments are fixed.

Medium

SKILL.md:100-111

Ruby/shell backtick execution

```bash

The fenced block creates an annotated Git tag. This changes local release state and must use the user-approved version.

Risk Factors

📁 Filesystem access (8)

PLAYBOOK.md:11 PLAYBOOK.md:21 references/git-commit-guidelines.md:266 references/git-commit-guidelines.md:300 references/git-commit-guidelines.md:394 SKILL.md:11 SKILL.md:19 SKILL.md:37

⚙️ External commands (36)

🌐 Network access (1)

SKILL.md:108

Audited by: codex View Audit History →

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/dimon94-npm-release/audits/9?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/dimon94-npm-release/security.svg)](https://skillstore.io/skills/dimon94-npm-release?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/dimon94-npm-release?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/dimon94-npm-release/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/dimon94-npm-release.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

Dimon94. (2026). npm-release security audit report (audit version 9) [Author version 1.1.0]. Skillstore. https://skillstore.io/skills/dimon94-npm-release/audits/9

BibTeX citation

@techreport{dimon94-dimon94-npm-release-2026,
  author = {Dimon94},
  title = {npm-release security audit report (audit version 9)},
  institution = {Skillstore},
  year = {2026},
  number = {9},
  url = {https://skillstore.io/skills/dimon94-npm-release/audits/9},
  note = {Author version 1.1.0}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "npm-release security audit report (audit version 9)"
version: "1.1.0"
type: report
authors:
  - name: "Dimon94"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/dimon94-npm-release/audits/9"
identifiers:
  - type: other
    value: "skillstore:dimon94-npm-release:audit:9"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: Medium

Architecture

100

Maintainability

Content

Community

Spec Compliance

What You Can Build

Prepare a maintenance release

Validate a clean branch, choose a patch version, update release files, and produce a reviewable commit and tag.

Publish an approved release

Run dry checks, push the approved branch and tag, publish to npm, and verify registry parity.

Recover a failed release

Assess local, remote, and registry state after failure, then select a controlled retry or rollback path.

Try These Prompts

Prepare a patch release

Prepare a patch release for cc-devflow. Inspect the repository, show the proposed version and changelog changes, and stop before pushing or publishing.

Create a release candidate

Prepare a minor release from the current approved branch. Run dry checks, create the release commit and tag, then request confirmation before network actions.

Audit version parity

Audit this release candidate for version parity across package files, changelog, commit, tag, and npm registry. Report blockers without changing state.

Recover a failed publication

Recover from this failed release: [paste error]. Determine registry, Git, and local state, propose the least destructive recovery, and wait for approval.

Best Practices

Confirm the exact worktree, branch, package, version, and registry before changing release state.
Require explicit approval immediately before remote pushes, publication, package execution, unpublish, or tag deletion.
Preserve failed release evidence and reconcile every package, changelog, commit, tag, and registry version.

Avoid

Do not release from a dirty or unapproved branch.
Do not skip npm identity checks, repository verification, or publication dry-runs.
Do not unpublish packages or delete tags to conceal a failed release.