agentleFS
anivaranivar/agentic-sdlc/AGENTS.md

agentic-sdlc

AGENTS.md0 starsChanged 37 days agoMITView on GitHub

For agents working in or on this repository. The skills under skills/ are the product; this file is about changing the product. - One plan step at a time. A change says which rule ids it touches. - Commit only when just check exits 0: ruff, the test suite, agentic-sdlc validate, agentic-sdlc check-skills, agentic-sdlc lint-voice, agentic-sdlc coverage --check and claude plugin validate --strict . (TEST-5). - Every commit, push and post waits for its own go-ahead (ASK-1, ASK-2, ASK-3). Stage…

The file

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

4 rules. About 0 are common, 0 are distinctive, and 4 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.

  • 4

    Very specific

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

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

    Commit only when just check exits 0: ruff, the test suite, agentic-sdlc validate, agentic-sdlc check-skills, agentic-sdlc lint-voice, …

    line 9
  2. Very specific:

    Every commit, push and post waits for its own go-ahead (ASK-1, ASK-2, ASK-3).

    line 12
  3. Very specific:

    Every rule with hook in its mechanisms carries examples in the registry, which tests/test_operability.py runs through the guard, and a case …

    line 21
  4. Very specific:

    Every skills/*/SKILL.md cites existing rule ids, lists in metadata.rules exactly the ids its body cites, has name equal to its folder, a …

    line 30

≈ “Common” is an estimate: at least 1 in 5 of the 41,581 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

agentic-sdlc: rules that bind

For agents working in or on this repository. The skills under skills/ are the product; this file is about changing the product.

How to work

  • One plan step at a time. A change says which rule ids it touches.
  • Commit only when just check exits 0: ruff, the test suite, agentic-sdlc validate, agentic-sdlc check-skills, agentic-sdlc lint-voice, agentic-sdlc coverage --check and claude plugin validate --strict . (TEST-5).
  • Every commit, push and post waits for its own go-ahead (ASK-1, ASK-2, ASK-3). Stage by path (STAGE-1). No tool attribution in commit or pull request text (ATTR-1). Never --no-verify (GUARD-1).

Rules

  1. rules/registry.json is the single source of rules. A new rule gets the next id in its prefix, a statement with an RFC 2119 word, a mechanism list, an owner skill and since. An id is never reused or renumbered; a retired rule is marked deprecated with replaced_by.
  2. Every rule with hook in its mechanisms carries examples in the registry, which tests/test_operability.py runs through the guard, and a case in tests/test_hook.py or tests/test_operability.py when it changes the hook contract.
  3. The hook stays standard-library Python that runs on 3.9. No dependency is added to the runtime path. tests/ run on 3.9 and 3.14 in CI and on the stock macOS interpreter.
  4. command.py parses; guard.py decides; text.py matches; hook.py and cli.py adapt. A new mechanism goes into those modules, not into the adapters.
  5. docs/coverage.md is generated. Run agentic-sdlc coverage after a registry change; CI fails when it is stale.
  6. Every skills/*/SKILL.md cites existing rule ids, lists in metadata.rules exactly the ids its body cites, has name equal to its folder, a description under 1024 characters, and a license line; a skill rewritten from another carries a NOTICE with the source's copyright line. check-skills enforces the first four.
  7. The repository tree carries no attribution patterns and no key-shaped literals; check-skills scans for both. It also refuses any token the maintainer lists in AGENTIC_SDLC_FORBIDDEN (CI) or .agentic-sdlc-forbidden.txt (local, gitignored).
  8. Text in README.md, docs/ and skills/ passes lint-voice --fail-on fail. A line that must quote a banned word carries voice-lint: skip in an HTML comment.
  9. Actions in workflows are pinned by commit sha with persist-credentials: false, and every workflow declares permissions.
  10. A tag-triggered workflow, when one is added, carries if: github.event.created so a moved tag cannot run it again.

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.