agentleFS
ifer47ifer47/markeron/.cursor/skills/release/SKILL.md

release

Skill1.2k starsChanged 5 months agoMITView on GitHub

MarkerOn release workflow. Use when the user asks to release, publish, bump version, create a tag, or cut a new version. Never release manually.

  • Commits and pushes

193 other projects use a version of this.

Trending

Quiet since July.thin dataabout the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 0 mentionsApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 2 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 0 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the ifer47/markeron repository that our weekly crawl found: only 2 in all, so this is a hint, not a trend. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about ifer47/markeron

The biggest 2 of 2 mentions linking to the repository that our crawl found. Each line is their own headline.

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

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 183 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Do not hand-edit version in four files — use npm run release

    line 63
  2. Distinctive:

    Do not git tag / git push tags manually unless fixing a failed release

    line 64
  3. Distinctive:

    Do not write release notes by hand unless user explicitly asks to edit after publish

    line 65
  4. Very specific:

    If release notes job fails, fix .github/workflows/release.yml on master, delete + recreate tag (see skill cross-platform-tauri-ui not …

    line 73

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

MarkerOn Release

Single entry point

Always use the release script — never manually bump version, commit, or tag.

# 1. Pre-flight (optional, also runs inside release)
npm run release:check

# 2. Dry run
npm run release patch --dry-run

# 3. Publish (patch | minor | major)
npm run release patch

The script automatically:

  1. Asserts clean git tree + master branch
  2. Runs the same checks as CI (build:fe, test, lint, format, cargo fmt --check)
  3. Bumps package.json, package-lock.json, Cargo.toml, Cargo.lock
  4. Commits chore(release): vX.Y.Z
  5. Tags vX.Y.Z and pushes branch + tag
  6. Triggers GitHub Actions Release workflow (multi-platform build + upload)

Release notes format (automatic)

Configured in:

FileRole
.github/release.ymlCategory titles (✨ New, 🛠 Fixes, …) for GitHub API
.github/workflows/release.ymlHeading normalization + git-log fallback when no PR notes

Output format:

## What's New in vX.Y.Z

### ✨ New
- ...

### 🛠 Fixes
- ...

### 🧹 Improvements
- ...

**Full Changelog**: https://github.com/ifer47/markeron/compare/vA.B.C...vX.Y.Z

Release notes are derived from Conventional Commits since the previous tag. Use npm run commit (czg) for daily commits so notes categorize correctly.

Agent rules

  • Do not hand-edit version in four files — use npm run release
  • Do not git tag / git push tags manually unless fixing a failed release
  • Do not write release notes by hand unless user explicitly asks to edit after publish
  • Pick bump level: patch (fixes), minor (features), major (breaking)
  • Requires gh CLI authenticated (gh auth login)

After release

Monitor: https://github.com/ifer47/markeron/actions/workflows/release.yml

If release notes job fails, fix .github/workflows/release.yml on master, delete + recreate tag (see skill cross-platform-tauri-ui not needed — use release workflow fix + retag).

Prerequisites

  • Node >= 20, Rust stable, gh CLI
  • On Windows: no bash required for release (Node script is cross-platform)

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.