release-prep

Name: release-prep
Availability: InStock
Author: Wendeus

Generate changelog entries, PR descriptions, and rollback plans from feature reports.

Updated Aug 23, 2026

Search Tags:#automation #git #workflow #changelog #rollback #release #pr-description

Ready to run

npx skills add https://github.com/wendeus0/AI-dotfiles --skill release-prep-wendeus0

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release-prep
Source: https://github.com/wendeus0/AI-dotfiles/tree/main/core/skills/release-prep
Command: npx skills add https://github.com/wendeus0/AI-dotfiles --skill release-prep-wendeus0

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orquestra a geração de artefatos de entrega após a escrita de relatórios de feature, incluindo changelog entries, PR descriptions e rollback plans, reduzindo a coordenação manual entre equipes.

Core Features & Use Cases

Geração automática de changelog entries, descrições de PR e rollback plans com base em critérios de READY_FOR_COMMIT e conteúdo de SPEC/REPORT.
Orquestra fluxos entre artifacts de release, garantindo consistência e governança antes de merge ou release.
Suporte a cenários de pré-commit e validação de risco para reduzir retrabalho manual e falhas de entrega.

Quick Start

Execute release-prep logo após o relatório de feature estar pronto para gerar artefatos de release.

Frequently Asked Questions about release-prep

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

FAQPage Schema

How do I automate changelog entry generation and PR description creation for feature releases?▼

Automating changelog entry generation and PR description creation requires orchestrating release artifacts from feature reports. It generates changelog entries, PR descriptions, and rollback plans automatically based on READY_FOR_COMMIT criteria and SPEC.md content.

What is a release rollback plan and when do I need to generate one?▼

A release rollback plan defines steps to revert a deployment if failures occur. You generate one when preparing release artifacts after feature reports, ensuring governance and safe recovery before merge or release.

How do I validate release risk and gate artifacts before a Git merge?▼

Validating release risk involves gating artifacts based on READY_FOR_COMMIT status and risk criteria extracted from feature reports. This ensures only validated artifacts proceed to merge or release.

Do I need SPEC.md and CHANGELOG.md files to generate release artifacts?▼

Yes, generating release artifacts requires access to feature reports, CHANGELOG.md, and SPEC.md. These files determine risks and produce artifacts meeting governance and rollback requirements.

What's the best way to orchestrate end-to-end release workflows across multiple feature writers?▼

The best way to orchestrate release workflows is using an automation tool that gates artifacts based on READY_FOR_COMMIT status. It coordinates individual writers and validates risk criteria across features before release.

When should I not use automated release preparation for my Git workflow?▼

Avoid automated release preparation when feature reports, CHANGELOG.md, or SPEC.md are unavailable or incomplete. Without these inputs, the tool cannot accurately determine risks or generate compliant rollback plans.