Hi HN,

I built an open-source tool called production-readiness: https://github.com/chuanjin/production-readiness

It analyzes a repository and generates a production readiness report that surfaces operational design risks the way senior engineers often do in reviews. It does not lint code or enforce policy. The focus is on design-level risks such as weak rollback strategies, fragile observability, unsafe migrations, and missing operational safeguards.

The goal is to turn tacit senior judgment into deterministic, repeatable signals that teams can run on every project.

I’d really appreciate feedback from people who’ve run production systems. In particular, I’m interested in gaps you think are critical, and whether this kind of tool would fit real workflows.

Thanks for reading.