fleet-codifying-disciplines

Codifying disciplines identifies gaps where a repo relies on memory or prose, then proposes executable enforcement via hooks, lint rules, and CLAUDE.md guidance with tests. It generates testable diffs and committed artifacts to replace ad-hoc processes.

Automating code quality checks involves selecting enforcement surfaces like git hooks or lint rules to guard against memory-based gaps. This skill evaluates your repo to propose the appropriate surface, producing a testable codification with a thorough test suite.

You can codify recurring lessons like running tests before commit by scanning for uncodified disciplines and generating executable checks. The skill produces testable diffs and committed artifacts, aligning each enforcer with a documented surface choice.

Choosing an enforcement surface depends on the specific discipline being codified. The skill uses a decision tree process to evaluate whether a hook, lint rule, check, or documentation best enforces the rule, documenting the surface choice in the output.

Yes, ensuring each proposed enforcer includes a thorough test suite is a core part of the process. It produces testable codifications to guarantee coverage and verify that the newly generated hooks and checks function correctly.