agentleFS
ubisoftubisoft/Sharpmake/AGENTS.md

Sharpmake

AGENTS.md1.1k starsChanged 3 months agoApache-2.0View on GitHub

Trending

Quiet this year.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: 0 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 0 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the ubisoft/Sharpmake repository that our weekly crawl found: only 4 in all, so this is a hint, not a trend. There is no adoption data for this file yet.
  • Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.

    Of the AGENTS.md files we read, the 31,774 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 repositoryOne other file it gives its agents.

The file

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

3 rules. About 0 are common, 2 are distinctive, and 1 is 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.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Distinctive:

    Use TDD when making changes in this repo.

    line 2
  2. Distinctive:

    Run the full test suite before declaring a task done.

    line 3
  3. Very specific:

    Default configuration is Release.

    line 6

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

Collaboration guidelines

  • Use TDD when making changes in this repo.
  • Run the full test suite before declaring a task done.

Build & test

  • Default configuration is Release; Debug is also allowed (-c Debug).
  • Build: dotnet build Sharpmake.sln /p:Configuration=Release /p:Platform="Any CPU"
  • Unit tests (NUnit): dotnet test Sharpmake.UnitTests -c Release
  • Public API tests: dotnet test Sharpmake.PublicApiTests -c Release
  • Regression tests (compare samples output to reference): python regression_test.py after building

Generated outputs (don't hand-edit)

  • Samples reference output: regenerate with UpdateSamplesOutput.bat
  • Verified public API snapshot: regenerate with UpdateVerifiedPublicApi.bat when the public API intentionally changes

Layout

  • Sharpmake/: core, Sharpmake.Generators/: generators, Sharpmake.Platforms/: platforms
  • Sharpmake.Application/: entry point, samples/: sample definitions, docs/: documentation
  • Adding a sample: see docs/Samples.md

Further reading (only when relevant)

  • Writing or changing Sharpmake definitions (targets, projects, samples): read docs/Guidelines.md.
  • Adding a platform or changing test/reference-output workflow: read CONTRIBUTING.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.