agentsclimarketplace

Git release tagging

Skill planifest/planifest-framework/planifest-framework/external-skills/git-release-tagging

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

Install
npx -y skills add planifest/planifest-framework --skill git-release-tagging

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

Create immutable release tags and traceable release notes from Git history. Use when release cuts require consistent tag naming, immutability guarantees, and bounded changelog traceability; do not use for CI workflow design or application behavior implementation.

SKILL.md

2.2 KB, 379 tokens by cl100k_base, as published. Nobody here has run it

Git Release Tagging

Overview

Use this skill to cut releases with immutable tags and auditable change boundaries.

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

  • Versioning and immutability rules:
    • references/tag-versioning-and-immutability.md

Templates And Assets

  • Release tagging runbook:
    • assets/release-tagging-runbook-template.md
  • Release notes template:
    • assets/release-notes-template.md

Inputs To Gather

  • Target release commit SHA and readiness evidence.
  • Versioning policy and reserved tag namespace.
  • Approval requirements and release communication needs.
  • Rollback strategy if release validation fails post-cut.

Deliverables

  • Annotated release tag bound to a specific commit.
  • Release notes mapped to bounded commit range.
  • Verification record for tag integrity and publication status.
  • Traceable release artifact metadata for audit.

Workflow

  1. Validate preconditions using assets/release-tagging-runbook-template.md.
  2. Confirm naming and immutability constraints from references/tag-versioning-and-immutability.md.
  3. Create annotated release tag and verify target commit binding.
  4. Draft and publish release notes with assets/release-notes-template.md.
  5. Record post-cut verification and handoff artifacts.

Quality Standard

  • Tag naming follows one consistent policy.
  • Published tag is immutable and never re-pointed.
  • Release notes are bounded, accurate, and actionable.
  • Release cut can be traced from tag -> commit range -> notes.

Failure Conditions

  • Stop when release commit readiness is not proven.
  • Stop when tag naming collides with existing published tags.
  • Escalate when immutability cannot be guaranteed on current hosting setup.

What ships with it: 1 file

11.3 KB alongside SKILL.md

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.