feat(chapter-19): add API linting with security rules
Chapter: 19 - Automated review. Plain-English map: Add ESLint for the API workspace, including TypeScript and security-oriented rules. Why it matters: Linters catch repetitive mistakes before a human reviewer spends attention on them. That frees review time for product and architecture questions. Principle: Automate the boring parts of code review. Precedent borrowed: Open-source CI hygiene and the fork report's broad hardening pattern. Upstream base: willchen96/mike@d39f580. Original local commit: 276d1fa.
| Repository | amal66/mike |
|---|---|
| Author | Amal <mamalanand3@gmail.com> |
| Authored | |
| Parents | 8664afc9 |
| Stats | 2 files changed , +65 , -1 |
| Part of | Add supply-chain audit ratchet and Dependabot |
Capture this commit into my fork
Download a Markdown prompt that tells Claude how to port this
exact commit into your working tree. Run it via
claude -p < capture-commit-93b1f1a0.md
from inside the repo you want the change in.