Skip to content

JPeetz/agent-skills / skills/git-release/release-management

release-management

Verified

Use this skill when preparing a new software release — version bumping, changelog generation, git tag workflows, release notes drafting, semantic versioning decisions, and CI release pipeline management. Covers the full release lifecycle from version selection to distribution.

FileKindSize
CHANGELOG.mdmarkdown531 B
LICENSEother979 B
SKILL.mdskill md9.4 KB
evals/evals.jsonconfig3.8 KB

evals/evals.json

View on GitHub
{
  "skill": "release-management",
  "version": "1.0.0",
  "cases": [
    {
      "id": "rm-001",
      "description": "Should trigger: determine the next semantic version bump",
      "input": "Since v1.1.0 we merged a breaking API change (removed a deprecated endpoint) and two bug fixes. What version should we release?",
      "shouldTrigger": true,
      "expect": "Applies SemVer bump rules — breaking change forces MAJOR — then walks the release workflow",
      "assertions": [
        "Bumps to 2.0.0, not 1.2.0 or 1.1.2",
        "Explains MAJOR/MINOR/PATCH mapping and the highest-category tiebreaker",
        "Cites the rule: once published, never modify a version's tag"
      ]
    },
    {
      "id": "rm-002",
      "description": "Should trigger: changelog maintenance per Keep a Changelog",
      "input": "Update the changelog for our next release: promote the Unreleased section, add the date, and link the version header.",
      "shouldTrigger": true,
      "expect": "Uses the Keep a Changelog structure (Added/Changed/Deprecated/Removed/Fixed/Security), promotes [Unreleased], adds date and tag comparison link",
      "assertions": [
        "Promotes [Unreleased] to the new version header",
        "Adds the release date and tag comparison link",
        "Verifies every change in the release has a changelog entry"
      ]
    },
    {
      "id": "rm-003",
      "description": "Should trigger: tag a release and create a GitHub/GitLab release",
      "input": "Cut v1.2.0: update manifests, commit, create a signed tag, push, and publish release notes.",
      "shouldTrigger": true,
      "expect": "Executes the release workflow: version bump in manifest files, chore(release) commit, signed tag, push, gh release create with notes file",
      "assertions": [
        "Updates version in package.json / pyproject.toml / VERSION",
        "Creates a signed tag (git tag -s v1.2.0)",
        "Uses gh release create with --notes-file CHANGELOG.md",
        "Merges the release branch with --no-ff and deletes it"
      ]
    },
    {
      "id": "rm-004",
      "description": "Should trigger: hotfix release workflow off the release tag",
      "input": "Critical production bug — we need a patch release now, and the fix must also land on main.",
      "shouldTrigger": true,
      "expect": "Runs the hotfix workflow: branch from the release tag (not main), cherry-pick the fix, patch bump, changelog entry under [Fixed], then cherry-pick back to main",
      "assertions": [
        "Branches from the release tag, not main",
        "Increments the patch version and adds a [Fixed] changelog entry",
        "Cherry-picks the hotfix back to main after release"
      ]
    },
    {
      "id": "rm-005",
      "description": "Should trigger: rollback planning before deployment",
      "input": "We're deploying v2.0.0 with a schema migration. Prepare the rollback plan.",
      "shouldTrigger": true,
      "expect": "Documents the rollback plan: trigger signal, rollback command, reversible migration check, verification, communication; selects the right strategy (DB migration revert here)",
      "assertions": [
        "Records rollback trigger, command, and verification steps",
        "Checks whether the data migration is reversible",
        "Selects database migration revert as the strategy for schema changes"
      ]
    },
    {
      "id": "rm-006",
      "description": "Not trigger: ordinary feature development with no release intent",
      "input": "Add a dark mode toggle to the settings page and write tests for it.",
      "shouldTrigger": false,
      "expect": "Does not enter the release workflow; handled as regular feature work",
      "assertions": [
        "No version bump, tagging, or changelog workflow invoked",
        "No release branch or CI release pipeline steps run"
      ]
    }
  ]
}
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall