agentsclimarketplace

Github release management

Skill planifest/planifest-framework/planifest-framework/external-skills/github-release-management

A specification framework for agentic development. Agents build from complete specs - not guesses.

Install
npx -y skills add planifest/planifest-framework --skill github-release-management

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Package and publish GitHub Releases with exact version/tag mapping, accurate release notes, and artifact integrity controls. Use when release publication on GitHub must be prepared or updated; do not use for non-GitHub runtime architecture or data-layer design.

SKILL.md

2.3 KB, as published. Nobody here has run it

Github Release Management

Overview

Use this skill to publish GitHub Releases that are accurate, traceable, and operationally usable by consumers.

Scope Boundaries

  • Use this skill when the task matches the trigger condition described in description.
  • Do not use this skill when the primary task falls outside this skill's domain.

Shared References

  • Release note structure guidance:
    • references/release-note-format.md

Templates And Assets

  • Release publication checklist:
    • assets/github-release-checklist.md

Inputs To Gather

  • Version target and release tag/commit mapping.
  • Changelog sources (PRs, commits, issues).
  • Artifact inventory, integrity policy, and compatibility notes.
  • Approval and communication requirements.

Deliverables

  • Draft/final GitHub Release package.
  • Release notes with upgrade and breaking-change guidance.
  • Verified artifact links and integrity evidence.
  • Post-release verification record.

Workflow

  1. Confirm release scope and freeze target commit.
  2. Generate notes with scripts/draft_release_notes.py.
  3. Validate notes format and completeness via references/release-note-format.md.
  4. Verify publication readiness with assets/github-release-checklist.md.
  5. Publish release and capture verification/follow-up actions.

Scripts

  • Generate draft notes from commit range:
    • python3 scripts/draft_release_notes.py --repo . --version v1.2.3 --from-ref <base_ref> --to-ref HEAD
  • Write output file:
    • python3 scripts/draft_release_notes.py --repo . --version v1.2.3 --from-ref <base_ref> --to-ref HEAD --out /tmp/release-notes.md

Quality Standard

  • Release notes reflect shipped changes without ambiguity.
  • Version/tag mapping is exact and immutable.
  • Breaking changes and migration guidance are explicit.
  • Artifacts are available and integrity-verified.

Failure Conditions

  • Stop when release scope, version, or tag mapping is inconsistent.
  • Stop when artifact integrity cannot be verified.
  • Escalate when breaking-change guidance is incomplete for public release.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.