skills.rest
masakinihirota
masakinihirotaCOMMUNITY
Explore all skills by this author →
𝕏@masakinihirotaGitHub

release-workflow

Guides safe production releases with pre-merge checks, version bumps, and git operations.

Updated Jul 21, 2026
Search Tags:#git#versioning#checklist#deployment#release#pnpm#merge
One-click install
npx skills add https://github.com/masakinihirota/2026src-ni --skill release-workflow-masakinihirota
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-workflow
Source: https://github.com/masakinihirota/2026src-ni/tree/main/.agents/skills/release-workflow
Command: npx skills add https://github.com/masakinihirota/2026src-ni --skill release-workflow-masakinihirota

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Releasing code to production without a consistent checklist leads to broken builds, unpatched vulnerabilities, and out-of-sync branches. This Skill provides a repeatable protocol for merging changes into the main branch safely. ## Core Features & Use Cases - Pre-Release Checklist: Runs lint, format, security audit (pnpm audit), type checks, and build verification before any merge to main. - Release Execution: Standardizes merging to main, semantic version bumping (major/minor/patch), and pushing tags. - Post-Release Sync: Keeps the development branch synchronized with main after every release. - Troubleshooting Guidance: Covers push hook failures (--no-verify) and temporary type-error workarounds. - Use Case: Before shipping a new feature, run through the checklist to catch a High-severity vulnerability and a failing build, then merge, bump the minor version, and push tags in the correct order. ## Quick Start Use the release-workflow skill to walk me through releasing my current development branch to main, including all pre-release checks and the version bump.

Frequently Asked Questions about release-workflow

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

FAQPage Schema
How do I safely merge a development branch into main?▼

Run lint, format, audit, type check, and build verification first, then checkout main, pull the latest changes, and merge the development branch. Finish with a version bump and push with tags.

What checks should run before releasing code to production?▼

Run pnpm lint:fix, format:fix, pnpm audit at moderate level, type checking, and a full build. Critical and High vulnerabilities must be fixed, and a failing build blocks the release entirely.

How do I bump the version when releasing with npm?▼

Use npm version with major, minor, or patch after merging into main. This updates the package version and creates a git tag, which you then push using git push origin main --tags.

Why does my git push fail in a hook when local builds pass?▼

Push hooks can fail due to timeouts or environment differences even when local lint and build succeed. You can bypass the hook with git push --no-verify once you have confirmed the checks pass locally.

How do I keep a development branch in sync after a release?▼

After pushing main, checkout the development branch, merge main into it, and push. This prevents divergence and merge conflicts in future development cycles.

Related Skills

Explore More Software Engineering Skills→
queen-of-codequeen-of-code
8

git-workflow

Standardize Git workflows with conventional commits and branch protection rules.

Community
Intermediate
DayoptDayopt

releasing

Automate version selection, duplicate checks, release notes, and tagging in PR-based release workflows.

Official
Advanced
shin0720shin0720

auto-canary

Automate pre-deployment verification including builds, E2E tests, and browser checks.

Community
Intermediate
marquesfelipmarquesfelip

automated-versioning

Automate semantic version bumps from conventional commits in CI/CD pipelines.

Community
Advanced