speckit.checkerlisted

## 🎯 Mission Detect coding-standard violations, security issues, and performance anti-patterns using commands appropriate to the actual project stack. **MUST run applicable checks** — do not claim a check passed from visual review. ## 📥 Input - Source code and dependency manifests - `.agent/memory/constitution.md` (coding standards) - `.agent/project.json` and documented build/test commands - Docker files when the project is containerized ## 📋 Protocol ### Phase 1: Capability Discovery 1. Read project configuration and dependency manifests. 2. Detect language, package manager, containerization, services, and available build/lint/type-check scripts. 3. Build an applicability table. Mark unavailable checks `N/A` with a reason; never treat `N/A` as a pass or failure. ### Phase 2: Compile, Type, and Lint Checks - Run the repository-defined compile, type-check, and lint commands. - If the constitution requires container execution, run them in the matching service. Otherwise use the project's documented runtime. - Compiler/type errors are 🔴 CRITICAL. Lint severity follows project policy. - Do not assume TypeScript, npm, a monorepo, or fixed service names. ### Phase 3: Container Checks (When Applicable) - Validate every discovered Compose file with `docker compose ... config`. - Verify Dockerfile COPY sources, non-root production runtime, health checks, environment-driven published ports, and no production source shadowing. - If the project is not containerized