agentleFS
Sign inStart free
ARM-softwareARM-software/CMSIS_6/AGENTS.md

CMSIS_6

AGENTS.md486 starsChanged 6 months agoApache-2.0View on GitHub

- Run CMSIS-Core tests in the Ubuntu 24.04 dev container. Do not install test dependencies on the host. - Read TESTING.md before selecting or running tests. It contains the container setup, matrix syntax, supported values, and license caveats. - Inspect the diff and run the smallest matrix that exercises the changed code. Do not run the complete matrix by default. Documentation-only changes do not require firmware tests unless they alter commands or test configuration. - When CMSIS tests are relevant,…

  • 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,542 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

Show its rules and text

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

13 rules. About 0 are common, 8 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run CMSIS-Core tests in the Ubuntu 24.04 dev container.

    line 5
  2. Very specific:

    Read TESTING.md before selecting or running tests.

    line 7
  3. Distinctive:

    Do not run the complete matrix by default.

    line 10
  4. Very specific:

    When CMSIS tests are relevant, select at least an affected core, a compiler, and an optimization level.

    line 12
  5. Distinctive:

    Add Clang for shared compiler abstractions, intrinsics, or inline assembly.

    line 16
  6. Distinctive:

    Add AC6 for Arm Compiler-specific paths when the required license is available.

    line 17
  7. Very specific:

    Add speed, size, or all optimization levels for code-generation or optimization-sensitive changes.

    line 19
  8. Distinctive:

    Add secure and non-secure variants for TrustZone changes.

    line 21
  9. Distinctive:

    Add representative M-profile generations for shared Core-M changes.

    line 22
  10. Distinctive:

    Add the affected A-profile or R-profile core for Core-A or Core-R changes.

    line 23
  11. Very specific:

    Run CoreValidation build run when runtime behavior, startup, system, exception, interrupt, or security behavior may have changed.

    line 24
  12. Distinctive:

    If a requested compiler, model, or core is blocked by a missing tool or license, record the exact blocker and continue with the other …

    line 30
  13. Very specific:

    Before handoff, report the exact commands and matrix combinations run, their pass/fail/skip totals, any filtered or blocked combinations, …

    line 33

≈ “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

Repository agent instructions

Test verification

  • Run CMSIS-Core tests in the Ubuntu 24.04 dev container. Do not install test dependencies on the host.
  • Read TESTING.md before selecting or running tests. It contains the container setup, matrix syntax, supported values, and license caveats.
  • Inspect the diff and run the smallest matrix that exercises the changed code. Do not run the complete matrix by default. Documentation-only changes do not require firmware tests unless they alter commands or test configuration.
  • When CMSIS tests are relevant, select at least an affected core, a compiler, and an optimization level. Start with GCC and none unless the change points to a different combination.
  • Expand the selection when applicable:
    • Add Clang for shared compiler abstractions, intrinsics, or inline assembly.
    • Add AC6 for Arm Compiler-specific paths when the required license is available.
    • Add speed, size, or all optimization levels for code-generation or optimization-sensitive changes.
    • Add secure and non-secure variants for TrustZone changes.
    • Add representative M-profile generations for shared Core-M changes.
    • Add the affected A-profile or R-profile core for Core-A or Core-R changes.
    • Run CoreValidation build run when runtime behavior, startup, system, exception, interrupt, or security behavior may have changed.
  • Quote wildcard selectors such as -d "CM33*" so the shell does not expand them. Repeat -c, -d, or -o to select multiple values.
  • Build a CoreValidation configuration before running it. build run is the preferred form for a fresh verification.
  • If a requested compiler, model, or core is blocked by a missing tool or license, record the exact blocker and continue with the other relevant configurations. Do not report an environment blocker as a source failure.
  • Before handoff, report the exact commands and matrix combinations run, their pass/fail/skip totals, any filtered or blocked combinations, and whether the worktree gained generated files.
  • Preserve pre-existing worktree changes. Remove only generated files created by the current test run, after confirming their paths with git status.

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