armada
CLAUDE.md9 starsChanged 5 months agoMITView on GitHub
Contributor and release rules live in CONTRIBUTING.md — read it before opening a PR.
In this repository3 other files it gives its agents.
- armada-nodeSkill
- armada-orchestratorSkill
- armada-workerSkill
The file
Files
Project Guide — armada-ai
Contributor and release rules live in CONTRIBUTING.md — read it before opening a PR.
Critical reminders for agents
- Never push to
main. Releases to Test PyPI fire only when a PR is merged intomain(.github/workflows/release.yml). - PR title must start with
feat:/fix:/perf:/ci:/chore:(lowercase, with colon) or no release runs.docs:does not trigger a release. - Bump
versioninpyproject.tomlin every releasable PR — Test PyPI rejects duplicate versions, and the failure is otherwise silent.
Quality gates
ruff check armada_ai/
pytest --cov=armada_aiDoes 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.

