release-engineer

Automate software releases with preflight checks, changelogs, versioning, and registry publishing.

4|1|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/AreteDriver/ai-skills --skill release-engineer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-engineer
Source: https://github.com/AreteDriver/ai-skills/tree/main/agents/analysis/release-engineer
Command: npx skills add https://github.com/AreteDriver/ai-skills --skill release-engineer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires build, twine, git, gh, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the complex and error-prone process of releasing software, ensuring readiness, generating documentation, and managing versioning.

Core Features & Use Cases

  • Release Readiness Checks: Verifies code health, documentation, metadata, security, and CI status before release.
  • Automated Versioning & Tagging: Bumps versions, creates Git tags, and commits changes according to semantic versioning.
  • Changelog Generation: Automatically creates or updates the CHANGELOG.md file based on git history.
  • Publishing: Supports publishing to package registries like PyPI, npm, and crates.io.
  • Use Case: After successfully merging a new feature, use this Skill to automatically run preflight checks, tag a new minor version, generate the changelog entry, and publish the package to npm.

Quick Start

Use the release engineer skill to perform a preflight check on the repository located at /path/to/my/repo.

Frequently Asked Questions about release-engineer

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

FAQPage Schema
How do I automate changelog generation and version bumping before publishing?▼

Automate changelog generation and version bumping by running preflight checks, creating Git tags, and updating CHANGELOG.md based on git history before publishing to package registries.

Can I publish packages to PyPI, npm, and crates.io using a single release pipeline?▼

Yes, you can publish packages to PyPI, npm, and crates.io using a single release pipeline that automates preflight checks, semantic versioning, and registry publishing.

What preflight checks are needed for a secure CI/CD release?▼

Preflight checks for a secure CI/CD release verify code health, documentation completeness, metadata accuracy, security compliance, and CI integration status before versioning and publishing.

Does this release automation tool work with GitHub CLI and twine?▼

Yes, this release automation tool works with GitHub CLI and twine, utilizing dependencies like build, git, and gh to manage versioning, tagging, and package publishing.

How do I handle hotfix releases across a portfolio of software projects?▼

Handle hotfix releases across a software portfolio by using dedicated hotfix and portfolio-wide assessment modes to verify readiness, bump patch versions, and publish updates.

What is the best way to ship software with confidence using automated release engineering?▼

Ship software with confidence using automated release engineering by enforcing preflight checks, generating changelogs, managing semantic versioning, and handling registry publishing.