agentleFS
rguiurguiu/armada/CLAUDE.md

armada

CLAUDE.md9 starsChanged 5 months agoMITView on GitHub

Contributor and release rules live in CONTRIBUTING.md — read it before opening a PR.

The file

Files
CLAUDE.md

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 into main (.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 version in pyproject.toml in every releasable PR — Test PyPI rejects duplicate versions, and the failure is otherwise silent.

Quality gates

ruff check armada_ai/
pytest --cov=armada_ai

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.