agentsclimarketplace

Release process

Skill niksavis/basicly/.claude/skills/release-process

One-command harness distribution for coding agents — a versioned YAML catalog projected into agent instructions, skills, and deterministic git gates.

Install
npx -y skills add niksavis/basicly --skill release-process

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

2 things to look at

  • 24 days oldThe repository was created 24 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 1 stars1 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

Prepare and publish semantic version releases using this repository's changelog-driven workflow. Use this when asked to cut a release, update CHANGELOG.md for a tag, review release notes quality, create/push tags, or verify GitHub release status.

SKILL.md

4.5 KB, as published. Nobody here has run it

Release Process

Run the repository release flow end-to-end with semantic tags and dated changelog sections.

Use basicly release — do not hand-run the preparation steps

Everything up to and including the annotated tag is automated (basicly release, component 9). Run it instead of typing the steps below:

basicly release 0.6.0 --issue <beads-id> --dry-run   # pre-flight; writes nothing
basicly release 0.6.0 --issue <beads-id>             # bump, regenerate, pins, changelog, commit, tag

It bumps the single-sourced __version__, regenerates the version-stamped projections, rewrites the @vX.Y.Z pins in README.md, site/index.html and both bootstrap shims, upserts the dated CHANGELOG.md section, commits, and creates the annotated tag. It never pushes.

Three things it deliberately does not do, which stay with you:

  • Push. Publishing is irreversible; run the two git push commands it prints.
  • Curate the changelog. It guarantees the section exists and is dated and lint-clean; the ### Highlights prose is yours to write before pushing.
  • Decide the version. Pass it explicitly; the command refuses one that does not move forward.

It refuses before writing anything on a dirty tree, a non-forward version, an existing tag, a bad date, an unknown --issue, a commit subject the commit-msg gate would reject, or a linked worktree (tags are shared with the primary checkout). A failure after the first write restores the tree, so a half-released repo needs no git reset --hard.

--autonomous --root <epic> is the delegated form and needs an L3 grant inside its spend ceiling with green lights-out preconditions; pass --shipping <node> to name the node whose gates are checked, because an open epic's own verify gate is never green.

The manual workflow below remains the reference for what the command automates and for the publication half.

Scope

This skill handles release preparation and publication for this repository.

It is not for:

  • Editing unrelated product features.
  • Rewriting git history.
  • Skipping quality gates.

Inputs

  • Target semantic tag (for example v0.1.1).
  • Release date in ISO format (YYYY-MM-DD).
  • Optional manual edits to changelog highlights before tagging.

Outputs

  • Updated CHANGELOG.md section for the target tag.
  • Tag pushed to origin.
  • GitHub release created by workflow with notes sourced from changelog.
  • Verification summary with run URL and release URL.

Workflow

  1. Verify branch state and quality gates.
  • Confirm working tree is clean.
  • Confirm required checks pass locally (pre-commit, tests) when relevant.
  1. Ensure release changes are committed first.
  • Commit any release workflow/tooling updates before generating changelog for the new tag.
  1. Generate changelog section.
  • Run:
  • uv run python .scripts/generate_release_changelog.py --tag vX.Y.Z --date YYYY-MM-DD
  • This computes commit delta from previous semantic tag to HEAD.
  1. Review changelog text for end-user clarity.
  • Keep a concise ### Highlights section.
  • Keep ### Commit delta (auto-generated) for traceability.
  • Ensure heading format is exact: ## vX.Y.Z - YYYY-MM-DD.
  1. Commit changelog update.
  • git add CHANGELOG.md
  • git commit -m "docs(release): update changelog for <release>"
  1. Push main branch.
  • git push origin main
  1. Create annotated semantic tag with date.
  • git tag -a vX.Y.Z -m "vX.Y.Z (YYYY-MM-DD)"
  • git push origin vX.Y.Z
  1. Verify release publication.
  • Check release workflow run status.
  • Confirm GitHub release body matches the tag section from CHANGELOG.md plus the pinned uvx install line.

Guardrails

  • Never force-push or rewrite history for release flow unless explicitly requested.
  • Never tag from a dirty working tree.
  • Never skip CI/quality gate failures.
  • Do not include user-specific local paths or secrets in changelog/release notes.

Trigger Examples

Should trigger:

  • "Cut v0.1.2 release and publish notes."
  • "Generate release notes from changelog and tag."
  • "Prepare next semantic release with date and push tag."

Should not trigger:

  • "Fix this installer bug in prerequisites.py."
  • "Refactor tmux config keybindings."
  • "Explain how CHANGELOG works conceptually."

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.