A cross-provider release-writing skill that gathers Git history, manifests, changelogs, and validation evidence, drafts user-focused notes, and changes GitHub release state only with explicit authorization.
publish-verified-github-release is a AI-agent skill created to make a real workflow clearer, faster, and easier to trust. It turns a focused product idea into something people can use, evaluate, and understand without needing to inspect the source code.
Why publish-verified-github-release exists
Commit logs are implementation-centric and can lead release authors to omit user impact, invent compatibility, or choose the wrong comparison boundary.
The goal is not simply to add another tool. publish-verified-github-release is designed to reduce the friction around that problem and give people a more dependable way to complete the work.
What it delivers
- Agents can turn repository history into scoped notes.
- Exclude unsupported names/compatibility/test claims.
- Flag breaking changes.
- Hand off final notes or an authorized release URL with evidence.
The experience
Turns verified repository evidence into trustworthy GitHub release notes and authorized releases.
The project brings the important parts of the workflow into one coherent experience. Its interface and behavior are shaped around the people using it, while the implementation stays focused on predictable results and honest feedback.
What to know
Every product has boundaries. These are the most important considerations for publish-verified-github-release:
- Tag/version/range ambiguity can materially change the release.
- Only user-visible changes supported by commits, diffs, issues, or changelogs belong in notes.
- Creating/editing a GitHub release is a remote mutation distinct from drafting.
These limitations are presented openly so visitors can understand where the project works well, what it depends on, and what may change in future versions.
Current status
Published npm package v0.2.0. The current release demonstrates the core value of the project and the main end-to-end experience.
My role was agent workflow design and automation engineering, covering agent workflow, validation automation, and packaging. The related case study explains the decisions and delivery process in greater depth for visitors who want the engineering story behind the product.