Rules in markdown vs rules in CI: what I measured in my own repositories

Описание и применение

В статье описывается, как автор использовал инструмент rebar для переноса правил из markdown в CI, что привело к 100% соблюдению правил и блокировке некорректных PR.

Задача

AI coding agents often ignore written standards, leading to hardcoded values, missing stack components, and incomplete documentation.

Результат

After integrating rebar, rule compliance rose from near zero to 100% for enforced rules. AI co-author trailers decreased, and CI failures prevented merges that violated governance.

Рабочий процесс

• 1. Install Node 22+. 2. Run npx github:Navesz/rebar . to format and run gate rules. 3. Run npx -p github:Navesz/rebar rebar-security . for security checks. 4. Ensure CI workflow includes rebar checks as required checks. 5. Monitor CI logs for rule compliance and adjust rules as needed.

Доказательства

The short version, as the README puts it: a rule written in markdown has close to zero compliance, and a rule in CI has 100%.

Источник

rebar-check · prumo ✓ editorconfig has .editorconfig ✗ dependabot automated dependency updates no dependabot, no renovate ✓ ci has CI ✓ ci-gates CI reaches the verification the repository declares – typecheck has a typecheck script no TypeScript here 11 of 13 · 1 not applicable

Источник