agentleFS
antickantick/skills/AGENTS.md

skills

AGENTS.md0 starsChanged 50 days agoMITView on GitHub

Treat skills/*/SKILL.md as the canonical skill set. Keep packs.json, SKILLS.md, the host plugin manifests, pi-extension/commands.json, skills/antick/references/catalogue.md, and the website catalogue and icons in website/src/lib/ synchronized with it. Run npm test, node --test website/tests/*.test.mjs, and npm pack --dry-run after catalogue changes. After completing and verifying a task that changes files, stage only the changes made for that task and create a local Conventional Commit with a type prefix such as feat, fix, or docs. Preserve unrelated user changes and report the…

The file

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

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

  • 3

    Very specific

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

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

    Treat skills/*/SKILL.md as the canonical skill set.

    line 3
  2. Very specific:

    Run npm test, node --test website/tests/*.test.mjs, and npm pack --dry-run after catalogue changes.

    line 8
  3. Very specific:

    After completing and verifying a task that changes files, stage only the changes made for that task and create a local Conventional Commit …

    line 11
  4. Distinctive:

    Never push commits unless the user explicitly asks you to push.

    line 16

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

Agent Notes

Treat skills/*/SKILL.md as the canonical skill set. Keep packs.json, SKILLS.md, the host plugin manifests, pi-extension/commands.json, skills/antick/references/catalogue.md, and the website catalogue and icons in website/src/lib/ synchronized with it.

Run npm test, node --test website/tests/*.test.mjs, and npm pack --dry-run after catalogue changes.

After completing and verifying a task that changes files, stage only the changes made for that task and create a local Conventional Commit with a type prefix such as feat, fix, or docs. Preserve unrelated user changes and report the commit hash and message in the final response.

Never push commits unless the user explicitly asks you to push.

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.