agentleFS
elsa-workflowselsa-workflows/elsa-studio/AGENTS.md

elsa-studio

AGENTS.md302 starsChanged 4 months agoMITView on GitHub

Keep repository-wide guidance feature-neutral. Feature-specific requirements, plans, and tasks belong under their feature directory in specs/. Before opening a PR, read .github/reviewers.md: Greptile is advisory (it reviews automatically; nobody waits for its score), request at most one additional advisory reviewer from the list once the PR is open, and merge only on the gate described there (Elsa 3 Code Review APPROVE + HIGH @ <head sha> plus green CI, merge pinned to that SHA).

The file

We split this AGENTS.md 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
  1. Very specific:

    Keep repository-wide guidance feature-neutral.

    line 3

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

Repository instructions

Keep repository-wide guidance feature-neutral. Feature-specific requirements, plans, and tasks belong under their feature directory in specs/.

Before opening a PR, read .github/reviewers.md: Greptile is advisory (it reviews automatically; nobody waits for its score), request at most one additional advisory reviewer from the list once the PR is open, and merge only on the gate described there (Elsa 3 Code Review APPROVE + HIGH @ <head sha> plus green CI, merge pinned to that SHA).

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.