agentleFS
Sign inStart free
VuDZVuDZ/RoslynMcpServer/.cursor/rules/roslyn-mcp-github-release.mdc

RoslynMcpServer / rules

Cursor rule8 starsChanged 45 days agoMITView on GitHub

GitHub Releases are dispatched by a human; agents never push tags

  • Commits and pushes

The file

We split this roslyn-mcp-github-release.mdc into the rules it gives an agent

3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

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

    Do not git tag, git push, or gh release create for a product release.

    line 8
  2. Very specific:

    When the user asks to выпусти релиз / пометь релизным / cut a GitHub Release: read .cursor/skills/prepare-github-release/SKILL.md and run …

    line 12
  3. Very specific:

    Do not replace test-suite.yml with one sequential dotnet test.

    line 20

≈ “Common” is an estimate: at least 1 in 5 of the 6,668 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
roslyn-mcp-github-release.mdc
---
description: GitHub Releases are dispatched by a human; agents never push tags
alwaysApply: true
---

# GitHub Releases (this repo)

Do **not** `git tag`, `git push`, or `gh release create` for a product release.
The agent cannot unlock the SSH key. Tag + GitHub Release are created by
`.github/workflows/release.yml` after a human **Actions → Release → Run workflow**.

When the user asks to выпусти релиз / пометь релизным / cut a GitHub Release:
read `.cursor/skills/prepare-github-release/SKILL.md` and run
`.github/scripts/Get-ReleaseMetadata.ps1`. Do not invent a second release path.

Skip a binary release for docs/rules-only trees. Local version bumps stay
independent of GitHub Releases (several bugfixes may share one dispatch).

CI shards (AnalyzerLifecycle vs unit, remainder filter): `.cursor/rules/roslyn-mcp-ci.mdc`.
Do not replace `test-suite.yml` with one sequential `dotnet test`.

Attest **Release archives only** (`actions/attest-build-provenance` on `release`
after every `pack` artifact is present, before `gh release create`): the
`win-x64` zips and the `linux-x64` tar.gz files. Do not attest CI TRX. Job
`release` needs `id-token: write` and `attestations: write` in addition to
`contents: write`. This is provenance, not Authenticode.

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