agentleFS
Sign inStart free
delexwdelexw/motion-graphics-agent/.claude/skills/cut-release/SKILL.md

cut-release

Skill62 starsChanged 24 days agoMITView on GitHub

Cut a versioned release of this project: inspect changes, choose a semantic version, synchronize npm version files, write release notes, verify checks, merge through the repository's normal rules, tag, and publish a GitHub source release. Use for requests such as "cut a release", "release v1.2.3", or "ship a patch release"; ordinary commits and pushes do not invoke this workflow.

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.

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 36 edited versions we read keep these.

  • 2

    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
  • could be automatic: a setting could enforce it
  1. Distinctive:

    Read and execute these phases in order.

    line 21
  2. Distinctive:

    No desktop installers or compiled platform bundles exist in this project.

    line 38
  3. Very specific:

    Never force-push, reassign/delete an existing remote tag, use --no-verify, use an administrator protection bypass, or rewrite the user's …

    line 41

“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 a Release — Kiteva

Adapted from the source project's release skill. Keep its inspect → version → notes → verify → publish flow, using this project's actual toolchain and release surface.

An explicit request to cut a release authorizes the release-owned edits, staging, commits, PR, merge, tag and GitHub release described here. Copying, editing or reviewing this skill does not authorize executing a release. Follow user scope, repository instructions and execution permissions. Do not ask again for authorization already given, bypass branch protections, or silently include unrelated work.

Read first

  • Project shape: version owners, checks, distribution and CI.
  • Version selection: conventional commits and this repository's Behavioural: / Structural: prefixes.
  • Changelog format: read when writing notes.

Workflow

Read and execute these phases in order. Keep commands observable and report progress during CI waits; use bounded waits so new user input can be handled. Do not leave detached release commands running.

  1. Inspect and scope
  2. Create the release branch
  3. Synchronize versions
  4. Write release notes
  5. Verify and commit
  6. Push and merge through normal protection
  7. Verify release CI and publish
  8. Verify main and the published tag
  9. Clean up and report

The inherited phase filenames remain stable; Phase 5 does not tag, and Phase 6 merges before the tag is published in Phase 7.

Release boundaries

  • Ship a GitHub source release. The npm package is private; never run npm publish.
  • No desktop installers or compiled platform bundles exist in this project. Do not invent assets or claim Windows checks passed from local macOS results.
  • Derive repository identity from the current checkout. Never use a copied remote, username, absolute local path or credentials.
  • A failed check, duplicate tag, divergent branch, unavailable required CI or denied operation stops the dependent release steps. Preserve work and report the concrete blocker; do not keep pushing or publish anyway.
  • Never force-push, reassign/delete an existing remote tag, use --no-verify, use an administrator protection bypass, or rewrite the user's unrelated work.
  • The separately served demo, model weights, downloaded authoring skills, credentials and temporary test output are not release assets.

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