pharaoh-release

Generate structured changelogs and release notes from requirement-level changes.

24|Updated Feb 12, 2026

Search Tags:#automation #changelog #requirements #audit #release #traceability #baselining

Ready to run

npx skills add https://github.com/patdhlk/pharaoh --skill pharaoh-release

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pharaoh-release
Source: https://github.com/patdhlk/pharaoh/tree/main/skills/pharaoh-release
Command: npx skills add https://github.com/patdhlk/pharaoh --skill pharaoh-release

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Release processes can be error-prone and time-consuming without structured, auditable artifacts. Pharaoh-release automates the generation of release artifacts by analyzing changes across requirements, specifications, implementations, and tests to produce changelogs, release notes, and traceability metrics suitable for safety-critical audits.

Core Features & Use Cases

Generate incremental and full release changelogs by comparing baseline releases to HEAD.
Produce audit-ready traceability coverage reports showing how needs link across the project.
Gate release workflows with optional verification and MECE checks based on pharaoh.toml configuration.

Quick Start

Run the pharaoh-release process to generate a changelog and release notes for the current project state.

Frequently Asked Questions about pharaoh-release

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

FAQPage Schema

How do I automate release notes and traceability audits for versioned projects?▼

Automate release notes and traceability audits by comparing a baseline release to HEAD, identifying requirement-level changes, and generating structured changelogs with coverage metrics. This produces audit-ready artifacts suitable for safety-critical workflows without altering source directives.

What is traceability coverage gating in a release workflow?▼

Traceability coverage gating checks how project needs link across requirements, specifications, implementations, and tests before release. Configured via pharaoh.toml, it optionally applies verification and MECE checks to ensure completeness and auditability for safety-critical projects.

How do I generate a changelog comparing a baseline release to HEAD?▼

Generate a changelog comparing baseline to HEAD by running the pharaoh-release process, which reads pharaoh.toml for strictness settings and uses ubc diff when available to summarize requirement-level changes and produce structured release artifacts.

Can I use pharaoh-release for safety-critical audit projects?▼

Pharaoh-release is designed for safety-critical audits and versioned projects, producing audit-ready traceability coverage reports and structured changelogs. It satisfies audit constraints by reading strictness from pharaoh.toml and generating artifacts without modifying source directives.

Do I need pharaoh.toml configured to generate release notes?▼

Pharaoh.toml is required to define strictness settings and configure optional verification and MECE checks for release gating. The process reads this configuration to satisfy constraints and produce structured changelogs and traceability metrics accurately.

What is the best way to generate structured changelogs without altering source code?▼

Generate structured changelogs without altering source code by running the pharaoh-release process, which compares baseline to HEAD and computes traceability coverage. It produces release artifacts independently, ensuring source directives remain unmodified throughout the analysis.