agentleFS
Sign inStart free
rpraharajrpraharaj/ai-engineer/skills/cut-release/SKILL.md

cut-release

Skill1 starsChanged 16 days agoMITView on GitHub

Cut a version and run this repository's existing release or deploy path. Use when the user asks to release, deploy, tag, publish, or ship to production. Detect the path from the repo. Do not invent a pipeline. Do not publish unless asked.

  • Commits and pushes

36 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use quota-axi, iterate-pr and 3 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.
  • layer5ioSkill

    quota-axi

    Report local Claude, Codex, Cursor, GitHub Copilot, and Grok quota windows via the quota-axi CLI - remaining percentages, reset times, and provider status read from local auth sources, with no routing, recommendation, or provider mutation. Use before deciding whether it is safe to keep spending a provider's quota, when the user asks about usage, rate limits, or remaining quota, or when comparing local provider headroom.

    Also in 4 projects that use this

  • SentrySkill

    iterate-pr

    Iterate on a PR until actionable CI passes and high/medium review feedback is addressed. Use for PR CI failures, review feedback, or green-check loops; do not wait for human approval, draft status, or merge gates.

    Also in 4 projects that use this

  • layer5ioSkill

    gh-axi

    Operate GitHub through the gh-axi CLI - issues, pull requests, workflow runs, workflows, releases, repositories, labels, Projects (v2), Actions secrets and variables, search, and raw API access. Use whenever a task touches GitHub: listing or filing issues, reviewing or merging PRs, checking CI runs, triggering workflows, cutting releases, managing Projects boards, or managing Actions secrets/variables.

    Also in 4 projects that use this

  • kunchenguidSkill

    chrome-devtools-axi

    Control a Chrome browser session through the chrome-devtools-axi CLI - navigate, snapshot, click, fill forms, run JavaScript, inspect console and network, take screenshots, audit performance. Use whenever a task needs a real browser: opening or testing a web page, clicking through a flow, extracting page content, or debugging a website.

    Also in 4 projects that use this

  • kunchenguidSkill

    lavish

    Turn complex or visual agent responses into rich, reviewable HTML artifacts (HTML files) the user can annotate and send feedback on, using the lavish-axi CLI. Use when about to give a plan, comparison, diagram, table, code diff, report, or anything easier to grasp visually than as prose.

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

8 rules. 0 are common, 3 are distinctive, and 5 are very specific to this project.

  • 0

    Common

    Most of the 36 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 5

    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:

    Read AGENTS.md if present.

    line 15
  2. Very specific:

    Look for the first match that this repo already uses (README, Makefile, package.json scripts, CI job named release/deploy, existing tags):

    line 19
  3. Very specific:

    If you cannot find a path, write the notes with ship-notes if needed, report which release configuration is missing and any verified manual …

    line 27
  4. Very specific:

    If they have not run ready-to-merge on this change, say so.

    line 33
  5. Distinctive:

    Run the detected release/deploy command.

    line 39
  6. Very specific:

    Do not npm publish / pypi upload / store submit unless that command is the detected path and they asked to publish.

    line 43
  7. Distinctive:

    If the command would spend money or require a paid upgrade, stop and say what the user must do in their dashboard.

    line 45
  8. Very specific:

    Do not merge a PR unless they asked.

    line 58

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

Cut release

Publish this version using machinery this repo already has. Do not invent a deploy system. Do not enable paid cloud plans, change billing, or buy domains. ship-notes writes the notes; this skill runs the release.

Read AGENTS.md if present. If git is missing, stop.

Detect the path

Look for the first match that this repo already uses (README, Makefile, package.json scripts, CI job named release/deploy, existing tags):

  • A documented Release / Deploy command
  • make release / make deploy / just release (only if that target exists)
  • A release script in the manifest (release, deploy) this repo's CI already runs
  • A releaser already configured (goreleaser, semantic-release, changesets, cargo-release, or this repo's equivalent)
  • Host CLI release (gh release create, glab release create) only if that is how this repo already ships

If you cannot find a path, write the notes with ship-notes if needed, report which release configuration is missing and any verified manual steps, and stop. Do not present invented commands as exact instructions. Do not guess npm publish or a cloud deploy.

Preconditions

  • Working tree clean enough for this repo's release (no leftover secret files — engineering-bar Secret files)
  • User asked to publish / deploy / tag. Notes-only is ship-notes.
  • If they have not run ready-to-merge on this change, say so. Do not block a notes+tag they insisted on.

Run (only what they asked)

  1. ship-notes first if the changelog is stale and this repo keeps one.
  2. Version bump only if they asked or the existing release script does it. Update the authoritative version sources and derived lockfiles/manifests required by this repo's release tooling; respect per-package or workspace versioning.
  3. Run the detected release/deploy command. Keep the output.
  4. Tag only if they asked or the script tags. Do not --force a tag. Do not delete a published tag.
  5. Push tags / publish only if they asked and a remote exists.

Do not npm publish / pypi upload / store submit unless that command is the detected path and they asked to publish. Do not change account, billing, or plan settings.

If the command would spend money or require a paid upgrade, stop and say what the user must do in their dashboard.

Done

## Release
- Path (command):
- Version / tag:
- Notes: <path or n/a>
- Published: yes | no | not asked
- Output:

Do not merge a PR unless they asked. Next is usually handoff or stop.

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