publish-verified-github-release

skill

Turns verified repository evidence into trustworthy GitHub release notes and authorized releases.

Role: Agent workflow design and automation engineering
Scope: Agent workflow, validation automation, and packaging
Status: Published npm package v0.2.0

Problem

Commit logs are implementation-centric and can lead release authors to omit user impact, invent compatibility, or choose the wrong comparison boundary.

Constraints

C1
Tag/version/range ambiguity can materially change the release.
C2
Only user-visible changes supported by commits, diffs, issues, or changelogs belong in notes.
C3
Creating/editing a GitHub release is a remote mutation distinct from drafting.

Architecture

Git/tag/diff evidence collector; release-note rules and drafting workflow; optional GitHub release adapter with explicit output/validation report.

Skill workflow

Git/tag/diff evidence collector.

Automation

Release-note rules and drafting workflow.

Verification

Optional GitHub release adapter with explicit output/validation report.

Decisions

Resolve target and comparison boundary before prose

Resolve target and comparison boundary before prose.

Separate breaking changes from ordinary improvements

Separate breaking changes from ordinary improvements and qualify inferred impact.

Keep drafting read-only

Keep drafting read-only and gate remote release creation independently.

Contribution

Built release evidence collection.
Codified note structure and evidence rules.
Implemented uncertainty and authorization checkpoints.
Packaged portable installers and tests for release behavior.

Outcomes

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.

Verified stack

Agent Skills
JavaScript
Node.js
npm
GitHub Actions
CI/CD
Git

Working through something similar?

Share your challenge, scope, and timeline to start a focused conversation.

Discuss a project