EthanReedLabsEthanReedLabs/sulde/AGENTS.md

sulde

AGENTS.md99 starsChanged 24 days agoMITView on GitHub

See CONTRIBUTING.md for the commands and fork contribution workflow.

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

5 rules. About 0 are common, 1 is distinctive, and 4 are very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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
could be automatic: a setting could enforce it

Very specific:
Keep the main working checkout on local dev, the latest integrated development branch.
line 5
Very specific:
Start each task branch from local dev in a repository-local .worktrees/<task> worktree.
line 7
Very specific:
Commit task changes in that worktree.
line 8
Distinctive:
Do not merge failed, experimental, interrupted, or superseded candidates.
line 9
Very specific:
Verify the integrated dev tree before advancing main.
line 10

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

Branch and worktree discipline

Keep the main working checkout on local dev, the latest integrated development branch.
The upstream repository exposes only main. Keep dev and task branches local.
Start each task branch from local dev in a repository-local .worktrees/<task> worktree.
Commit task changes in that worktree. Run the scoped checks and merge the completed task into dev.
Do not merge failed, experimental, interrupted, or superseded candidates.
Verify the integrated dev tree before advancing main. Both the task and integration worktrees must be clean before merging.
main is the publication branch. Feature and repair changes reach it through dev; do not commit them directly to main.
Push only main to the upstream repository. Remove an old upstream task branch after its required commits are included in published main.
Resolve branch divergence on dev, verify the result, then advance main.

See CONTRIBUTING.md for the commands and fork contribution workflow.

Download now (ZIP)

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 28,693 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 repository28 other files it gives its agents.
- codex-preflight-scaffoldSkill
- configure-suldeSkill
- coordinator-maintenanceSkill
- curate-to-kbSkill
- dispatch-parallel-taskSkill
- handoff-code-reviewSkill
- multi-source-reviewSkill
- record-prd-supplementSkill
- reverse-source-completenessSkill
- sediment-from-codeSkill
- update-designSkill
- writing-task-mdSkill
- assignSkill
- bug-huntSkill
- code-reviewSkill
- crash-fixSkill
- handoffSkill
- parallel-devSkill
- perf-diagnoseSkill
- postmortemSkill
- ui-implSkill
- dispatch-taskSkill
- import-codex-sessionSkill
- intent-guardianSkill
- kb-searchSkill
- memory-distillSkill
- sedimentSkill
- sulde-add-sensitive-fileSkill

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