release

Automate pepcode releases across version bumps, tests, tagging, npm publishing, and GitHub releases.

Updated Feb 15, 2026
One-click install
npx skills add https://github.com/leejaedus/pepcode --skill release-leejaedus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/leejaedus/pepcode/tree/main/skills/release
Command: npx skills add https://github.com/leejaedus/pepcode --skill release-leejaedus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the end-to-end release workflow for pepcode across version bumps, tests, tagging, publishing, and release notes.

Core Features & Use Cases

  • Version bump across multiple files (package.json, installer references, tests, and docs)
  • Run tests and ensure all checks pass before publishing
  • Create and push Git tags, publish to npm, and generate a GitHub release
  • Verify release artifacts and release notes for stakeholders

Quick Start

Invoke the release workflow with a target version, for example /pepcode:release 2.4.0

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate an npm publish workflow with version bumps and git tags?

Automating an npm publish workflow requires bumping versions across multiple files, running tests, pushing git tags, and generating release notes. The release skill orchestrates this entire sequence end-to-end for pepcode projects.

What's the best way to bump versions across multiple files before a GitHub release?

Bumping versions across multiple files means updating package.json, installer references, tests, and docs simultaneously. The release workflow automates these cross-file updates to ensure consistency before creating a GitHub release.

Can I run tests automatically before publishing to npm?

Running tests before publishing to npm is a built-in step in the release workflow. It executes your test suite and ensures all checks pass before proceeding to git tagging and npm publishing.

How does pepcode release automation handle git tagging and release notes?

Pepcode release automation handles git tagging and release notes by creating and pushing a git tag for the target version, then generating a GitHub release with verified release notes for stakeholders.

Do I need any specific CI/CD pipeline setup to use this release workflow?

No specific CI/CD pipeline setup is required as a dependency. The release workflow operates independently to bump versions, run tests, tag commits, and publish to npm without external pipeline configuration.

Why should I use an automated release workflow instead of manual version bumping?

Automated release workflow prevents human error during manual version bumping by synchronizing updates across package.json, tests, and docs, verifying tests pass, and standardizing git tagging and npm publishing steps.