de-commit

Conventional commit messages require explicit type prefixes like feat, fix, ref, or docs, followed by a concise subject. This Skill enforces these coding standards, applying a 300-character limit per line to ensure version-control history remains readable and traceable.

Git commit footers can include issue references using Fixes or Refs tags, alongside optional AI authorship annotations in the commit notes. This Skill structures these mandatory frontmatter fields and footnotes to track task origins and co-authorship automatically.

Enforcing a 300-character line limit in git commit messages involves applying strict formatting rules to the subject line and body. This Skill acts as a guideline to restrict line length, ensuring conventional commits stay concise and readable across feature and refactor workflows.

Yes, the conventional commit guideline supports feature, fix, refactor, and docs workflows with explicit type rules. It ensures consistent git documentation and collaboration by validating commit types and enforcing mandatory frontmatter fields across these specific coding workflows.

Git commit messages lack traceability when they omit mandatory frontmatter fields and issue references in footnotes. This Skill solves the problem by enforcing conventional commits with strict type rules and team task referencing, improving version-control readability and historical tracking.

Yes, conventional commits can be extended to branch naming and workflow consistency. This Skill provides basic recommendations for branch naming alongside commit message rules, helping teams maintain unified documentation and coding standards across the entire version-control lifecycle.