coding-violation-log

What problem does it solve?

This Skill ensures that every coding violation, whether a layering violation, naming inconsistency, or architecture breach, is immediately logged and reviewed before continuing work, preventing the same errors from recurring.

Core Features & Use Cases

• Automatically create or update a coding-violations.md log when a user corrects a coding error (such as layering violations, naming nonconformities, or architecture breaches).
• Read and reference the log at the start of each coding session to ensure compliant changes, and increment occurrence counts for repeated issues.
• Provides Mermaid-based diagrams and a structured table format to clearly communicate root causes and corrective actions to the team.

Quick Start

When a user corrects a coding error, create or update docs/coding-violations.md and append a new record with type, description, file, first occurrence date, and count.