pamaga-agent-toolkit
AGENTS.md1 starsChanged 39 days agoMITView on GitHub
How to write skills, commands and agents here, and the checks to run before committing, are in docs/CONVENTIONS.md. Day-to-day work goes on dev: push there freely. When a change is ready, open a PR from dev to main. PRs run the checks, and merging to main cuts the release. Keep main releasable. main is protected: no direct pushes (admins included), only PRs whose four check jobs pass. The repository allows only merge commits; never re-enable squash or rebase merging: they…
- Commits and pushes
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 repository12 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- deep-reviewSkill
- find-bugSkill
- implement-planSkill
- make-planSkill
- make-roadmapSkill
- new-ticketSkill
- plan-pageSkill
- plans-conventionSkill
- research-topicSkill
- save-learningSkill
- ship-workSkill
The file
We split this AGENTS.md into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 38
Add [patch] only when the user asks for it.
- Distinctive: line 49
Never create, move or delete version tags or releases by hand, and do not write version numbers into files: the tag is the only source of …
≈ “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.
Files
pamaga-agent-toolkit
How to write skills, commands and agents here, and the checks to run before committing, are in docs/CONVENTIONS.md.
Branches
Day-to-day work goes on dev: push there freely. When a change is ready,
open a PR from dev to main. PRs run the checks, and merging to main
cuts the release. Keep main releasable.
main is protected: no direct pushes (admins included), only PRs whose
four check jobs pass. The repository allows only merge commits; never
re-enable squash or rebase merging: they rewrite the dev commits, so dev
stops containing the released tags and loses the [patch] markers (see
Versions). After the merge, bring dev up to main
so the next work starts from the release:
git switch dev && git pull && git merge --ff-only origin/main && git push.
Versions
Releases from main are semver tags 0.MINOR.PATCH (0.1.0, 0.2.0...).
The release job in .github/workflows/ci.yml turns every push to main
that passes CI into the next version, computed by scripts/next_release.py:
MINOR by default, or PATCH when a commit subject since the last release
contains [patch]. Release notes list
the commits since the previous release. The major stays 0 while the
toolkit is young; 1.0.0 will mark the stable interface.
The version is chosen when committing, and the choice is the user's:
MINOR(no marker): new or changed skills, commands, agents or installer behaviour. This is the default.PATCH: only fixes, typos and docs that change no behaviour. Put[patch]in the commit subject (the first line; case does not matter), e.g.Fix typo in ship-work [patch].
Add [patch] only when the user asks for it. One [patch] anywhere since
the last release makes the whole next release a PATCH, even if other
commits add features, so if a [patch] commit is already waiting on dev
and you add a feature, tell the user.
dev has no tags and no releases: a dev clone's version is its commit. The
installer labels it 0.2.0+3 (dev) when it is three commits past 0.2.0,
dev (abc1234) when no release is reachable, and compares origin/dev with
the clone to say when to pull. A clone on main only hears about newer
stable releases.
Never create, move or delete version tags or releases by hand, and do not write version numbers into files: the tag is the only source of truth.
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
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.