RoslynMcpServer / rules
Cursor rule8 starsChanged 46 days agoMITView on GitHub
GitHub Actions test jobs; do not serialize the full suite again
Where files are headingNew Cursor rule files have more rules about planning and tracking tasks, and fewer about code style.
Of the Cursor rule files we read, the 4,181 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository16 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/roslyn-mcp-build-sdk.mdcCursor rule
- .cursor/rules/roslyn-mcp-decompile.mdcCursor rule
- .cursor/rules/roslyn-mcp-dev-conventions.mdcCursor rule
- .cursor/rules/roslyn-mcp-docs-agents.mdcCursor rule
- .cursor/rules/roslyn-mcp-docs-lifecycle.mdcCursor rule
- .cursor/rules/roslyn-mcp-github-release.mdcCursor rule
- .cursor/rules/roslyn-mcp-overview.mdcCursor rule
- .cursor/rules/roslyn-mcp-paths.mdcCursor rule
- .cursor/rules/roslyn-mcp-pitfalls.mdcCursor rule
- .cursor/rules/roslyn-mcp-structural-tests.mdcCursor rule
- .cursor/rules/roslyn-mcp-tools.mdcCursor rule
- .cursor/rules/roslyn-mcp-version-bump.mdcCursor rule
- epoch-subagent-loopSkill
- epoch-subagent-loopSkill
- prepare-github-releaseSkill
The file
We split this roslyn-mcp-ci.mdc into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Do not fold CI back into one sequential dotnet test on the whole .sln to “save runners”.
≈ “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.
Files
---
description: GitHub Actions test jobs; do not serialize the full suite again
alwaysApply: true
---
# CI test jobs (this repo)
Canon: [`.github/workflows/test-suite.yml`](../../.github/workflows/test-suite.yml).
`ci.yml` and `release.yml` **call** that workflow. Do not copy a second `dotnet test` matrix.
The repo is **public** — GitHub-hosted minutes are not the limit (~20 concurrent jobs are).
Do **not** fold CI back into one sequential `dotnet test` on the whole `.sln` to “save runners”.
## What may not run in one testhost
`[CollectionDefinition("AnalyzerLifecycle", DisableParallelization = true)]` plus
`AnalyzerShadowPublisher`: one MSBuild lifecycle host / shadow dirs. In-process
xUnit threads will race. Unit tests (`Category!=AnalyzerLifecycle`) already parallelize
inside the testhost.
## Partition contract
One OS runs two shards. Within that OS the shards must not overlap. On Windows their union is every discovered test. On Ubuntu `unit` also excludes `RequiresWindows` (the task-01 inventory, four tests). That exclusion is a filter, so those tests are absent from the Linux TRX (`notExecuted` stays 0). Do not put them back into the Linux filter and do not mark them `[Fact(Skip)]`.
| OS | Shard | Filter | `ROSLYN_MCP_ANALYZER_LIFECYCLE` |
|---|---|---|---|
| `windows` | `unit` | `Category!=AnalyzerLifecycle` | unset |
| `windows` | `lifecycle` | `Category=AnalyzerLifecycle` | `1` |
| `ubuntu` | `unit` | `Category!=AnalyzerLifecycle&Category!=RequiresWindows` | unset |
| `ubuntu` | `lifecycle` | `Category=AnalyzerLifecycle` | `1` |
Display names: `unit (windows)`, `lifecycle (windows)`, `unit (ubuntu)`, `lifecycle (ubuntu)`. Artifacts: `trx-unit-windows`, `trx-lifecycle-windows`, `trx-unit-ubuntu`, `trx-lifecycle-ubuntu`. Caller checks in `ci.yml` / `release.yml` are prefixed with `tests /`.
A red job on either OS fails the workflow. Do not put `continue-on-error` back on Ubuntu. The ten consecutive Linux main-suite runs that allowed that are recorded in `docs/archive/linux-x64-support/evidence/task-02-linux-main-ten-runs.md`.
`AnalyzerLifecycleHostTests` is the **only** class carrying `Category=AnalyzerLifecycle`
(thirteen host methods). `Epoch1SemanticInventoryTests` is source-only, carries no trait, and
runs in `unit`. Do not add named per-epoch shards back, and do not leave an empty named shard.
`AnalyzerLifecycleFactAttribute` / `AnalyzerLifecycleTheoryAttribute` read the variable **before**
the host probe: anything other than `1` skips without starting an MSBuild host. MCP tools never set
it, so an agent must not pick these methods through `run_specific_test` — the run would skip.
`fail-fast: false`. Skip is a **job failure** (`.github/scripts/Assert-NoSkippedTests.ps1`), not a
green CI. Never weaken that script.
Pass `--filter` as a quoted env value (`"$env:FILTER"`). Bare `&` in PowerShell is the call operator.
JS actions must be Node 24 majors (`checkout@v6`, `setup-dotnet@v5`, `upload-artifact@v7`,
`download-artifact@v8`). Do not pin `@v4` of those — GitHub removes Node 20. Do not set
`ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION`. Hosted `windows-latest` is new enough.
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.