agentleFS
Sign inStart free
epullaepulla/patio/.agents/skills/release/SKILL.md

release

Skill2 starsChanged 13 days agoMITView on GitHub

Guides local app/executable builds and GitHub releases. Trigger on “release”, “cut/make a release”, “GitHub release”, “tag a version”, or “build the app/executables locally”.

  • Commits and pushes

196 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use create-agent-adapter, changelog-style and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • MicrosoftSkill

    create-agent-adapter

    Technical guide for creating a new Paperclip agent adapter. Use when building a new adapter package, adding support for a new AI coding tool (e.g. a new CLI agent, API-based agent, or custom process), or when modifying the adapter system. Covers the required interfaces, module structure, registration points, and conventions derived from the existing claude-local and codex-local adapters.

    Also in 5 projects that use this

  • GrinvSkill

    changelog-style

    Turn a commit range into CHANGELOG.md entries following common-changelog style. Use when finishing a PR or cutting a release, to write/fix the [Unreleased] section's entries — moving [Unreleased] under a new dated version heading is a separate, automated step (see the release skill / scripts/sync-version.ts), not this skill's job.

    Also in 4 projects that use this

  • GrinvSkill

    docs-consistency-check

    Check README/manifest.json/server.json/CHANGELOG.md/AGENTS.md and docs/*.md for drift against the actual registered tools and source. Use after adding, renaming, or removing a tool, or as part of a live-audit pass.

    Also in 4 projects that use this

  • Microsoft AzureSkill

    component-release

    Prepares a verifiable Agent Landing Zone UI release. Use for release branches, VERSION, changelog entries, tags, release notes, and compatibility evidence; never publish without explicit human approval.

    Also in 4 projects that use this

  • Microsoft AzureSkill

    documentation-consistency

    Keeps AI Landing Zone contributor, user, and operator documentation aligned with shipped Bicep behavior. Use for parameters, defaults, outputs, topology, deployment flow, operations, or releases.

    Also in 8 projects that use this

  • rivet-devSkill

    launch-graphics

    Generate agentOS marketing/launch graphics (launch & social heroes, code-snippet cards) from the committed generators in docs-internal/graphics. Use when asked to make, update, or render an agentOS launch image, social image, "agentOS Apps" graphic, or technical code-snippet image.

    Also in 3 projects that use this

  • +3 more from Grinv

The file

Show its rules and text

We split this skill into the rules it gives an agent

16 rules. 0 are common, 9 are distinctive, and 7 are very specific to this project.

  • 0

    Common

    Most of the 186 edited versions we read keep these.

  • 9

    Distinctive

    This author's own choices. Worth a look.

  • 7

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Distinctive:

    Use this workflow for local builds and tagged GitHub releases.

    line 8
  2. Distinctive:

    Run repo verification from AGENTS.md:

    line 12
  3. Distinctive:

    Stop and report any failed check.

    line 18
  4. Distinctive:

    Check git status --short. Require empty output.

    line 29
  5. Distinctive:

    Check git branch --show-current.

    line 31
  6. Very specific:

    Run git fetch, then inspect git status -sb.

    line 33
  7. Very specific:

    Run gh auth status. Require successful authentication.

    line 36
  8. Very specific:

    Read last tag with git describe --tags --abbrev=0.

    line 41
  9. Very specific:

    Before 1.0.0: ! or BREAKING CHANGE means minor.

    line 45
  10. Distinctive:

    Wait for user to confirm or override version before continuing.

    line 49
  11. Distinctive:

    Run full AGENTS.md verify list, in order:

    line 53
  12. Very specific:

    Wait for explicit user go.

    line 62
  13. Very specific:

    Never tag or push before go or when checks fail.

    line 63
  14. Very specific:

    After approval, run git tag -a vX.Y.Z -m "vX.Y.Z", then git push origin vX.Y.Z using confirmed version.

    line 64
  15. Distinctive:

    Never force-push, move or delete existing tags, edit published releases, or skip checks unless user explicitly asks.

    line 88
  16. Distinctive:

    Never repeat a failed release by moving its tag.

    line 90

“Common” is measured: kept by at least 6 in 10 of the 186 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

Release

Use this workflow for local builds and tagged GitHub releases. Never skip required checks.

Local build (no tag)

  1. Run repo verification from AGENTS.md:
    • gofmt -l internal — output must be empty.
    • go vet ./... && go test ./... -count=1
    • pnpm --dir web build
    • make app (macOS), make exe (Windows) or make linux
    • make release — CGO-free Windows compile check.
  2. Stop and report any failed check. Do not claim build succeeded.
  3. Optional: stamp a version with make app VERSION=<v>. Untagged builds default to dev.
  4. Smoke-test macOS build: build/bin/patio.app/Contents/MacOS/patio -d "$(mktemp -d)/test.db"
  5. Report build outputs in build/bin/.

GitHub release

Preconditions

  1. Check git status --short. Require empty output; otherwise refuse and explain uncommitted changes must be handled first.
  2. Check git branch --show-current. Require main; otherwise refuse and explain release must start from main.
  3. Run git fetch, then inspect git status -sb. Require branch equal to origin/main, with no ahead/behind count; otherwise refuse and explain sync with origin is required.
  4. Run gh auth status. Require successful authentication; otherwise refuse and explain GitHub CLI authentication is required.

Select version

  1. Read last tag with git describe --tags --abbrev=0. If none exists, propose v0.1.0 and review commits with git log --oneline HEAD.
  2. Otherwise inspect commits with git log --oneline <last>..HEAD.
  3. Propose next SemVer from those commits:
    • Before 1.0.0: ! or BREAKING CHANGE means minor; anything else (feat, fix, ui…) means patch.
    • From 1.0.0: ! or BREAKING CHANGE means major; any feat means minor; otherwise patch. Moving to 1.0.0 is a user decision, never proposed from commits. Present proposed tag and rationale.
  4. Wait for user to confirm or override version before continuing.

Verify and gate tag

  1. Run full AGENTS.md verify list, in order:
    • gofmt -l internal — output must be empty.
    • go vet ./... && go test ./... -count=1
    • pnpm --dir web build
    • make app
    • make release
  2. Any failure stops release. Report failing command and output; do not tag or push.
  3. Show exact tag and commit summary from git log --oneline <last>..HEAD (or git log --oneline HEAD for first release).
  4. Wait for explicit user go. A request to make a release is not this approval. Never tag or push before go or when checks fail.
  5. After approval, run git tag -a vX.Y.Z -m "vX.Y.Z", then git push origin vX.Y.Z using confirmed version.

Monitor and confirm

  1. Get latest workflow run: gh run list --workflow release.yml --limit 1.
  2. Watch its ID: gh run watch <id> --exit-status.
  3. On failure, run gh run view <id> --log-failed and report failure. Do not retag without user approval; deleting a pushed tag requires explicit approval.
  4. On success, check assets with gh release view vX.Y.Z --json assets -q '.assets[].name'.
  5. Require exactly these four names:
    • patio-darwin-arm64.zip
    • patio-darwin-amd64.zip
    • patio-windows-amd64.exe
    • patio-linux-amd64
  6. Workflow auto-generates release notes. Tag builds stamp version via make <target> VERSION=<tag> (-X main.version, macOS Info.plist); app shows version bottom-right and MCP serverInfo reports it.
  7. Manual workflow_dispatch builds upload artifacts only, create no release, and use version dev.

Never

  • Never force-push, move or delete existing tags, edit published releases, or skip checks unless user explicitly asks.
  • Never repeat a failed release by moving its tag. Require explicit user approval before deleting a pushed tag.

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