omk-coding

Automated coding discipline enforces test-driven development and code review by applying a phase-driven workflow with strict quality gates. This ensures every code change is minimal, tested, and self-reviewed before completion.

Maintaining coding discipline in worktrees and submodules requires applying automated quality checks across writing, editing, debugging, and refactoring tasks. This enforces minimal, tested changes regardless of the repository structure.

Start a phase-driven coding workflow by initializing your project environment and completing a mandatory deep-read protocol before making any code changes. This establishes guardrails against regressions.

Automated coding discipline works for refactoring and bug fixing by enforcing test execution and project conventions across all tasks. It ensures changes remain minimal and self-reviewed before claiming done.

Automated guardrails for code quality gates prevent technical debt by enforcing adherence to project conventions at the point of creation. This ensures every change satisfies test execution and self-review requirements.

Applying coding discipline checks requires a mandatory deep-read protocol to understand existing conventions before making changes. Skipping this environment setup phase breaks the guardrails against regressions.