skills.rest
maroffo
maroffoCOMMUNITY
Explore all skills by this author →
GitHub

releasing-software

Automate software release preparation with pre-flight verification and green CI checks.

16|2|Updated Nov 9, 2025
Search Tags:#git#ci/cd#versioning#deployment#release#tagging
One-click install
npx skills add https://github.com/maroffo/claude-forge --skill releasing-software
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: releasing-software
Source: https://github.com/maroffo/claude-forge/tree/main/skills/releasing-software
Command: npx skills add https://github.com/maroffo/claude-forge --skill releasing-software

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the software release process by ensuring all necessary pre-flight checks are completed, preventing common errors and maintaining a clean, trustworthy release history.

Core Features & Use Cases

  • Pre-Release Verification: Enforces a checklist including build paths, test coverage, local CI, documentation, release configuration, and Git state.
  • Release Procedure Guidance: Provides a step-by-step process for committing, pushing, tagging, and verifying releases, emphasizing the "NO TAG WITHOUT GREEN CI" rule.
  • Troubleshooting Common Failures: Offers solutions for frequent issues like incorrect build paths or missing test coverage.
  • Use Case: When preparing to release a new version of a software project, use this Skill to systematically verify all components and ensure a smooth, error-free deployment to production.

Quick Start

Use the releasing-software skill to prepare for a new release by running through the pre-release checklist and following the release procedure.

Frequently Asked Questions about releasing-software

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

FAQPage Schema
How do I prevent deploying a release tag when CI tests are failing?▼

To prevent deploying a release tag with failing tests, enforce a strict no-tag-without-green-CI policy. This requires running mandatory pre-flight checks for local CI, test coverage, and build configurations before pushing any Git tags.

What is the pre-release checklist for Git tagging and deployment?▼

The pre-release checklist for Git tagging verifies build paths, test coverage, local CI execution, documentation, release configuration, and Git state. Completing these checks ensures a clean deployment to production.

How do I automate versioning and tagging for software releases?▼

Automate versioning and tagging by following a guided release procedure that commits changes, pushes to the repository, applies tags, and verifies the deployment. This enforces pre-flight verification to maintain code quality.

Why does my CI/CD pipeline fail during the deployment step?▼

Your CI/CD pipeline might fail during deployment due to incorrect build paths or missing test coverage. Troubleshoot these common failures by verifying release configuration and ensuring local CI passes before tagging.

Do I need local CI to pass before creating a Git tag for production?▼

Yes, local CI must pass before creating a Git tag for production. Enforcing a no-tag-without-green-CI rule prevents common release errors and maintains a trustworthy release history.

Related Skills

Explore More Software Engineering Skills→
LuizfbmLuizfbm
1

using-git-worktrees

Create isolated Git worktrees with dependency installation and gitignore verification.

Community
Advanced
mkrlabsmkrlabs

github-release

Automate GitHub releases with tag validation and build checks.

Official
Advanced
FlexNetOSFlexNetOS

alpha

Execute predefined test scenarios in CI/CD environments.

Official
Basic
donnfelkerdonnfelker

hooks

Integrate custom shell scripts into Kamal deployment lifecycle hooks.

Community
Advanced