CI/CD bots and automated code review
One binary in a container, fast startup, no pip install step that breaks on a Tuesday.
The problem
Review bots summarise diffs, flag risky patterns, and suggest tests. Container images that
start with pip install -r requirements.txt are fragile CI citizens: a yanked package or
upstream metadata change turns green builds red.
Why Ecko
- Copy binary, run
- Multi-stage Docker: copy
eckoand your.eckosources. Startup is milliseconds, not minutes of dependency resolution. - Pattern matching
- Real
matchon AST-shaped data for deterministic checks; useaionly where semantics matter. - py() escape hatch
- Call an existing Python library when you must - without making Python the runtime for everything else.
In practice
FROM debian:bookworm-slim COPY ecko /usr/local/bin/ecko COPY review.ecko /app/review.ecko ENTRYPOINT ["ecko", "/app/review.ecko"]
Try it on your workload.