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
Most recently taken up by
- yicheng47/runnertheir own version, first seen Nov 13, 2026
- eugene1g/agent-safehousetheir own version, first seen Nov 12, 2026
- BlockRunAI/ClawRoutertheir own version, first seen Nov 11, 2026
- cubeplexai/cubeplextheir own version, first seen Nov 10, 2026
- bex-co/bextheir own version, first seen Nov 10, 2026
- Yeachan-Heo/oh-my-claudecodetheir own version, first seen Nov 9, 2026
Who's talking about ifer47/markeron
- ScoopInstaller/Scoop“[Bug] checkver github mode not working for url ending with #/dl.7z”GitHub · Jul 14, 2026
- ScoopInstaller/Extras“[Request]: MarkerOn”GitHub · Jul 14, 2026
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.
MicrosoftSkillcreate-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
GrinvSkillchangelog-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
GrinvSkilldocs-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 AzureSkillcomponent-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 AzureSkilldocumentation-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-devSkilllaunch-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
Other versions193 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 193
- paperclipai/paperclip★ 114ksame name
- modelcontextprotocol/servers★ 92ksame name
- remotion-dev/remotion★ 73ksame name
- traefik/traefik★ 66ksame name
- usememos/memos★ 64ksame name
- tw93/Pake★ 64ksame name
- amruthpillai/reactive-resume★ 46ksame name
- reactive-resume/reactive-resume★ 46ksame name
- AmruthPillai/Reactive-Resume★ 45ksame name
- Yeachan-Heo/oh-my-claudecode★ 41ksame name
183 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 repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/commit-conventions.mdcCursor rule
- .cursor/rules/cross-platform-ui-styles.mdcCursor rule
- .cursor/rules/i18n.mdcCursor rule
- .cursor/rules/node-toolchain.mdcCursor rule
- .cursor/rules/release-workflow.mdcCursor rule
- cross-platform-tauri-uiSkill
- grill-meSkill
- tauri-config-ipcSkill
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
- Very specific: line 63
Do not hand-edit version in four files — use npm run release
- Distinctive: line 64
Do not git tag / git push tags manually unless fixing a failed release
- Distinctive: line 65
Do not write release notes by hand unless user explicitly asks to edit after publish
- Very specific: line 73
If release notes job fails, fix .github/workflows/release.yml on master, delete + recreate tag (see skill cross-platform-tauri-ui not …
“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.
Files
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 patchThe script automatically:
- Asserts clean git tree +
masterbranch - Runs the same checks as CI (
build:fe, test, lint, format,cargo fmt --check) - Bumps
package.json,package-lock.json,Cargo.toml,Cargo.lock - Commits
chore(release): vX.Y.Z - Tags
vX.Y.Zand pushes branch + tag - Triggers GitHub Actions Release workflow (multi-platform build + upload)
Release notes format (automatic)
Configured in:
| File | Role |
.github/release.yml | Category titles (✨ New, 🛠 Fixes, …) for GitHub API |
.github/workflows/release.yml | Heading 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.ZRelease 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 pushtags 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
ghCLI 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,
ghCLI - On Windows: no bash required for release (Node script is cross-platform)
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
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.

