coding-guidelines-verify
Original:🇺🇸 English
Translated
1 scripts
Verify changes follow nearest-scoped AGENTS.md rules: group changed files by nested scope, auto-fix formatting, run lint/tests, and report violations. Use when the user wants scoped compliance checks for changed files.
13installs
Sourcejmerta/codex-skills
Added on
NPX Install
npx skill4agent add jmerta/codex-skills coding-guidelines-verifyTags
Translated version includes tags in frontmatterSKILL.md Content
View Translation Comparison →Coding guidelines verifier
Goal
Validate that changes follow the nearest nested :
AGENTS.md- default: changed files only
- default: auto-fix formatting before lint/tests
- monorepo-aware: each module’s is the source of truth for that scope
AGENTS.md
Workflow (checklist)
- Collect changed files (staged + unstaged + untracked).
- For each changed file, find the nearest parent .
AGENTS.md- If a file has no scoped , report it (suggest running
AGENTS.md).coding-guidelines-gen
- If a file has no scoped
- Parse the block (schema:
codex-guidelines).references/verifiable-block.md - Run, per scope:
- format (auto-fix) -> lint -> tests
- apply simple forbid rules (globs/regex) from the block
- Produce a short compliance report (template: ).
references/report-template.md
Automation
Use to group scopes, run commands, and report results.
scripts/verify_guidelines.py- If is not available or the script fails, tell the user and ask whether to install Python or proceed with a manual per-scope verification.
python
Deliverable
Provide:
- The per-scope compliance report (use ).
references/report-template.md - Any auto-fix formatting changes applied.
- Lint/test commands run and their results, plus any violations.