← ClaudeAtlas

developlisted

Project conventions and recurring gotchas for implementer agents working on agent-orchestrator, plus Rust-specific LLM gotchas. Use before opening a PR for any change in orchestrator/, tests/, docs/, or plans/, and for any change in a Rust codebase.
geserdugarov/agent-orchestrator · ★ 3 · AI & Automation · score 76
Install: claude install-skill geserdugarov/agent-orchestrator
# Developer skill — agent-orchestrator ## Commits - Conventional Commits: `<type>: <subject>` with one of `feat`, `fix`, `chore`, `docs`, `refactor`, `test`. - Subject line only — no body, no `Co-Authored-By` trailer, no extended description. One `-m` flag. - Imperative mood, short and specific. Match the style in `git log --oneline -20`. ## Pre-push checklist Before committing, run each of these and fix what they report: - `.venv/bin/python -m ruff check orchestrator tests` — recurring CI breakers: - **F401** (unused import): if the name is meant to be a re-export from `workflow.py`, alias it with `... as <name>` so ruff treats it as an explicit re-export instead of dead code. - **F541** (f-string without placeholders): use a plain string. - **F841** (unused local). - **E402** (module-level import not at top of file). - `git diff --check origin/main...HEAD` — catches trailing whitespace and stray blank lines at EOF. - `.venv/bin/python -m pytest` — full suite must pass. Do not assume any "known" failure is acceptable; if a test fails on your branch, first reproduce it on `origin/main` at the same SHA you branched from, and only then call it out in the PR as a baseline failure with the reproduction steps. Otherwise fix it. ## Refactoring `workflow.py` and the stage modules The facade pattern in `orchestrator/workflow.py` is load-bearing for tests. Get the boundary right: - `workflow.py` re-exports stage handlers and cross-module helpers under their original na