agentleFS
Sign inStart free
V-SongbirdV-Songbird/foundry/.agents/skills/cut-release/SKILL.md

cut-release

Skill4 starsChanged 10 days agoMITView on GitHub

Release one Foundry plugin, only when the user invokes it by name. Bumps the version and changelog in the plugin repository, pushes, then pins the pushed commit in the Foundry catalogs.

36 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use quota-axi, iterate-pr and 6 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

  • ThisIsSadeghiSkill

    verify-ui

    Verify UI implementation against Stitch design via a token audit (HTML ↔ Code, with X-component default-render checks) and an X-components compliance check.

    Also in 3 projects that use this

  • Other versions36 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 36

    1. ToolJet/ToolJet★ 41ksame name
    2. meshery/meshery★ 12ksame name
    3. danielmeppiel/apm★ 4.2ksame name
    4. microsoft/apm★ 4.2ksame name
    5. Screenly/Anthias★ 3.7ksame name
    6. Netflix/bpftop★ 2.7ksame name
    7. tansu-io/tansu★ 1.9ksame name
    8. fim-ai/fim-agent★ 1.6ksame name
    9. fim-ai/fim-one★ 1.6ksame name
    10. libredb/libredb-studio★ 1.3ksame name

    26 more not listed

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository5 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 36 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before taking release actions, read and follow the complete canonical release procedure.

    line 19
  2. Very specific:

    Run commands from the Foundry root, except step 4's pin check, which runs from the checkout that holds the release commit and takes the …

    line 30

“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

This is the Codex and Antigravity entrypoint for this repository's release procedure. Use it only when explicitly invoked, as $cut-release in Codex or /cut-release in Antigravity; take the plugin and requested version from the user's message. Codex reads the invocation policy from agents/openai.yaml, and Antigravity from disable-model-invocation above.

Before taking release actions, read and follow the complete canonical release procedure. The procedure is shared with Claude Code; do not duplicate its steps here.

Codex and Antigravity execution notes

  • Resolve the canonical link relative to this skill directory. If it is missing, stop and report the missing procedure rather than inventing a release workflow.
  • The canonical file's Claude-only frontmatter describes its discovery on that host; its release steps apply here. Interpret Read and Edit as the available file-reading and patch tools, not required tool names.
  • Run commands from the Foundry root, except step 4's pin check, which runs from the checkout that holds the release commit and takes the root's path. On Windows, use rg instead of the grep example. claude plugin validate and step 5's Claude Code check need the Claude Code CLI, step 5's Codex check the codex CLI, and agy plugin validate and step 5's Antigravity check the Antigravity CLI; when one is absent, report that check as not run instead of skipping it silently.
  • Preserve existing authorization. Before each commit or push, verify the user's release request authorizes that action and its scope, and review the staged diff and the branch to be pushed so unrelated work cannot be included silently. Preparing or porting this skill does not authorize a release.

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