tanaab-release

Automate release preparation, changelog drafting, and release-metadata decisions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Guides and accelerates release readiness by formalizing the tasks of release planning, changelog creation, and release contract decisions within the Tanaab framework.

Core Features & Use Cases

  • Release planning and versioning governance for consistent releases.
  • Changelog generation and release-notes drafting aligned with release contracts.
  • Release-facing repository metadata updates and governance across related repos.
  • Coordination with tanaab-github-actions and tanaab-testing when automation is in scope.

Quick Start

Run the release planning and changelog drafting workflow to prepare the next release metadata.

Frequently Asked Questions about tanaab-release

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

FAQPage Schema
How do I automate changelog drafting and release notes for consistent versioning?

Automated changelog drafting standardizes release notes by applying defined workflow templates and versioning governance. It enforces release readiness across repositories while ensuring consistent release metadata updates.

What is the best way to formalize release planning and repository metadata updates?

Release planning governance formalizes repository metadata updates by enforcing defined workflow steps and ownership relationships. This standardizes release readiness across related repositories within the coding hierarchy.

Can I use this release preparation workflow with GitHub Actions automation?

Yes, the release preparation workflow is compatible with tanaab-github-actions and related tooling. It coordinates with automation tools when GitHub Actions integration is in scope for your release process.

Does this release governance workflow require tanaab-testing to run?

No, tanaab-testing is not a required dependency for release governance. The workflow coordinates with tanaab-testing when automation is in scope, but operates independently to handle versioning and changelog generation.

How do I enforce ownership relationships when drafting release contracts?

Enforcing ownership relationships during release contract drafting relies on standardized workflow templates. The system delegates implementation details to appropriate sub-skills, ensuring release-facing repository updates maintain consistent ownership governance.