agentleFS
ifer47ifer47/markeron/.cursor/rules/release-workflow.mdc

markeron / rules

Cursor rule1.2k starsChanged 5 months agoMITView on GitHub

Release and versioning — always use npm run release, never manual tag/bump.

  • Commits and pushes

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.

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.

The file

We split this release-workflow.mdc into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    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. Very specific:

    When releasing MarkerOn, only use:

    line 11
  2. Distinctive:

    Write release notes before publish (CI generates them)

    line 27

≈ “Common” is an estimate: at least 1 in 5 of the 6,809 Cursor rule files we read have a rule of the same kind, not the same words. “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
release-workflow.mdc
---
description: Release and versioning — always use npm run release, never manual tag/bump.
globs: package.json,.github/workflows/release.yml,.github/release.yml,scripts/release.mjs
alwaysApply: false
---

# Release Workflow

## Mandatory command

When releasing MarkerOn, **only** use:

```bash
npm run release patch   # bug fixes (most common)
npm run release minor   # new features
npm run release major   # breaking changes
```

Optional dry run: `npm run release patch --dry-run`

Pre-check only: `npm run release:check`

## Never do manually

- Edit version in `package.json` / `Cargo.toml` / lockfiles by hand
- `git tag vX.Y.Z` + `git push origin vX.Y.Z` without the script
- Write release notes before publish (CI generates them)

## Commit format (feeds release notes)

Daily commits must follow Conventional Commits — use `npm run commit`:

| Prefix | Release section |
|--------|-----------------|
| `feat:` | ✨ New |
| `fix:` / `hotfix:` | 🛠 Fixes |
| `docs:` | 📚 Documentation |
| `ci:` / `build:` | 👷 CI |
| other | 🧹 Improvements |

## Config files (do not duplicate logic elsewhere)

- `scripts/release.mjs` — local release automation
- `.github/release.yml` — GitHub note categories
- `.github/workflows/release.yml` — CI build + note generation

Full details: `.cursor/skills/release/SKILL.md`

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.