m_code_rules_auditlisted

# m_code_rules_audit Audit code against the rules that actually exist in the repo and the deterministic checks that can be run safely. ## Contract Use `$ARGUMENTS` as the target file, directory, branch, diff, PR, or rule focus. Default mode is `report-only`. Do not edit code unless the user explicitly asks for fixes. Never claim a check passed unless it ran in this session or the user provided the result. ## Workflow ### 1. Determine scope If a target is given, audit that target. If no target is given: ```txt - audit the current working-tree diff - if there is no diff, audit the highest-risk project rules and structure ``` Inspect: ```txt - git status - git diff / changed files, when available - target files - nearby tests - relevant configs and docs ``` ### 2. Load rule sources in order Read applicable rules from: ```txt 1. User's explicit request 2. CLAUDE.md and .claude/CLAUDE.md 3. .claude/rules/**/*.md 4. nested CLAUDE.md files near target files 5. README, docs/architecture.md, ADRs, contribution guide 6. package/build scripts and test config 7. lint/typecheck/formatter configs 8. CI workflows 9. visible framework/repo conventions ``` If `AGENTS.md` exists but no `CLAUDE.md` imports or mirrors it, report that Claude Code may miss those instructions. If rules conflict, report the conflict. Do not silently choose the convenient rule. ### 3. Classify risk Mark these as high-risk areas: ```txt authentication authorization/permissions billing/payments migr