agentleFS
Sign inStart free
erraggyerraggy/oastools/.claude/skills/publish-release/SKILL.md

publish-release

Skill7 starsChanged 9 months agoMITView on GitHub

Publish a prepared release (phase 7). Usage: /publish-release <version>. Requires version argument. Wraps publish-release.sh for deterministic execution.

  • Commits and pushes

13 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

10 rules. 0 are common, 6 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 11 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before running this skill:

    line 14
  2. Very specific:

    Run /prepare-release <version> to complete phases 1-6

    line 16
  3. Very specific:

    Verify prepared notes exist at .release/notes-<version>.md

    line 17
  4. Distinctive:

    Ensure you're ready to publish (this is irreversible)

    line 19
  5. Distinctive:

    If no version is provided, stop and ask the user:

    line 27
  6. Very specific:

    If the version doesn't match the vX.Y.Z pattern, reject it:

    line 35
  7. Distinctive:

    Use the AskUserQuestion tool to confirm before proceeding:

    line 44
  8. Distinctive:

    Always confirm before publishing - releases are irreversible

    line 96
  9. Distinctive:

    If the script fails partway, check the error message for recovery steps

    line 97
  10. Very specific:

    NEVER: use gh release create - goreleaser creates the draft

    line 98

“Common” is measured: kept by at least 6 in 10 of the 11 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

publish-release

Publish a prepared release to GitHub. This is phase 7 of the release process.

Usage: /publish-release <version> (e.g., /publish-release v1.46.0)

Prerequisites

Before running this skill:

  1. Run /prepare-release <version> to complete phases 1-6
  2. Verify prepared notes exist at .release/notes-<version>.md
  3. Review the release notes in that file
  4. Ensure you're ready to publish (this is irreversible)

Process

⚠️ CRITICAL: This skill wraps publish-release.sh. Do NOT run release commands manually.

Step 1: Validate Version Argument

If no version is provided, stop and ask the user:

Error: Version argument required.
Usage: /publish-release <version>
Example: /publish-release v1.46.0

If the version doesn't match the vX.Y.Z pattern, reject it:

Error: Version must match vX.Y.Z pattern (e.g., v1.46.0)
Got: <invalid-version>

Step 2: Confirm with User

Use the AskUserQuestion tool to confirm before proceeding:

Ready to publish release **<version>**?

This will:
1. Create and push git tag <version>
2. Trigger goreleaser workflow
3. Wait for draft release with binaries
4. Publish the release (irreversible)

Proceed? [Yes / Cancel]

Step 3: Run the Publish Script

From the repository root, run:

.claude/scripts/publish-release.sh <version>

The script handles:

  1. Verifies on main branch
  2. Creates and pushes annotated tag
  3. Waits for goreleaser workflow
  4. Verifies draft has 8 assets (binaries + checksums)
  5. Reads prepared notes from .release/notes-<version>.md (fails if missing)
  6. Publishes with gh release edit --draft=false
  7. Verifies published release

Step 4: Report Results

On success, report:

✅ Release <version> published successfully!

View release: https://github.com/erraggy/oastools/releases/tag/<version>

The release includes:
- 8 binary assets for all platforms
- Enhanced release notes (from prepare step)
- Homebrew formula will update automatically

On failure, report the error and suggest recovery steps.

Important Notes

  • Version argument is required (no inference - you're publishing what you prepared)
  • Always confirm before publishing - releases are irreversible
  • If the script fails partway, check the error message for recovery steps
  • NEVER use gh release create - goreleaser creates the draft

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free