agentleFS
Sign inStart free
joslatjoslat/maf-doctor/CLAUDE.md

maf-doctor

CLAUDE.md14 starsChanged 3 months agoMITView on GitHub

Read AGENTS.md first: it maps the codebase, the self-update loop, and the coding standards. These are working notes on top of it. CI minutes and Copilot credits are limited. Run the gates locally so CI confirms rather than debugs: When registry entries change, also compile their examples against the real packages (needs nuget.org; the release and the one before it must be in the train lock): Batch commits on one branch and keep one PR open at a time. -…

We split this CLAUDE.md into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read AGENTS.md first: it maps the codebase, the self-update loop, and the coding standards.

    line 3
  2. Distinctive:

    When registry entries change, also compile their examples against the real packages (needs nuget.org.

    line 19

≈ “Common” is an estimate: at least 1 in 5 of the 25,680 CLAUDE.md 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
CLAUDE.md

CLAUDE.md

Read AGENTS.md first: it maps the codebase, the self-update loop, and the coding standards. These are working notes on top of it.

Before pushing

CI minutes and Copilot credits are limited. Run the gates locally so CI confirms rather than debugs:

dotnet test src/maf-autopilot.Tests/maf-autopilot.Tests.csproj -c Release -f net10.0
python3 -m pytest .github/scripts/tests -q
python3 .github/scripts/verify_crossfile_consistency.py
MAF_REGISTRY_PATH="$PWD/.github/skills/maf-obsolete-api-registry/registry.yaml" \
  dotnet src/maf-autopilot/bin/Release/net10.0/maf-doctor.dll verify-registry

When registry entries change, also compile their examples against the real packages (needs nuget.org; the release and the one before it must be in the train lock):

python3 .github/scripts/verify_registry_examples.py --old-version 1.22.0 --version 1.23.0 \
  --maf-doctor "dotnet src/maf-autopilot/bin/Release/net10.0/maf-doctor.dll"

Batch commits on one branch and keep one PR open at a time.

Gotchas

  • Build in Release. A running maf-doctor MCP server locks the Debug output. On Windows add -nodeReuse:false -p:UseSharedCompilation=false to avoid idle MSBuild nodes.
  • Doctor_ValidPath_ExitsZero can fail locally when %TEMP% is polluted; filter it out (--filter "FullyQualifiedName!~Doctor_ValidPath_ExitsZero").
  • Git Bash: prefix git show ref:path with MSYS_NO_PATHCONV=1. To run dotnet-inspect from Python on Windows, pass dotnet-inspect.cmd.
  • Escapes: writing C#, YAML or Python through a shell heredoc can turn \n and \-newline into literal line breaks. Use an editor tool for escape-heavy edits.
  • Unquoted YAML scalars in registry.yaml must not contain : ; quote them.
  • Diff from the merge-base (base...head) in PR gates. A two-dot diff against an advanced main attributes main's changes to the PR.
  • Watcher scaffold PRs (release-watcher/maf-*) must keep linear history and may only touch data paths; never merge main into them. To re-run their checks on a fresh merge ref, push a commit to the branch.

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.

Reviews can't be read right now.

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