coding-violation-log

To log coding violations, create or update a docs/coding-violations.md file by appending a record with the violation type, description, file path, first occurrence date, and occurrence count to prevent repeating mistakes.

Tracking layering violations and architecture breaches is best handled by maintaining a structured markdown log with Mermaid-based diagrams to clearly communicate root causes and corrective actions to the team.

You can automatically update a coding standards log by applying this workflow before coding starts, ensuring the existing log is read, updated with new violation details, and occurrence counts are incremented for repeated issues.

This coding violation tracking workflow requires no external dependencies or components, operating entirely by managing your coding standards documentation within the existing project repository.

You need to read the coding violations log at the start of each coding session to ensure compliant changes, reference past errors, and increment occurrence counts if you encounter repeated issues.

Yes, you can use Mermaid-based diagrams alongside a structured table format in your coding-violations.md file to clearly communicate the root causes of coding standards violations and their corrective actions.