What problem does it solve? Developers and agents working in the Archimedes repository hit recurring friction: Node and Python both live in a single conda env that is not on the base PATH, tests pass in CI but fail locally due to environment leakage, and the repo enforces a merge-commit-only branch policy that differs from common GitHub defaults. This Skill consolidates those operational rules so code is written, tested, and merged correctly the first time. ## Core Features & Use Cases - Environment setup: Explains that the archimedes conda env carries both Python and Node, and how to prepend its bin directory for non-interactive shells. - Hermetic test discipline: Codifies rules for writing tests with no .env dependence, no live Redis/Postgres, boundary mocking, and the exact env -i gate command reviewers run. - Branch and CI policy: Documents merge-commit-only merging, branch naming, commit message conventions, and which CI gates (ruff, pytest) actually block a PR. - Use Case: An agent starting work in the repo reads this Skill first, activates the env correctly, runs pytest -m "not integration" matching CI, and opens a PR that passes the quality gate without a failed CI round-trip. ## Quick Start Read this Skill before writing or running any code in the Archimedes repository, then follow its environment, testing, and merge instructions for your task.
