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

来源