coding-guidelines-verify

Nymbo's avatarfrom Nymbo

Verify changes follow nearest-scoped AGENTS.md rules: group changed files by nested scope, auto-fix formatting, run lint/tests, and report violations.

⭐1stars🔀0forks📁View on GitHub🕐Updated Dec 20, 2025
[Code Review]

When & Why to Use This Skill

The Coding Guidelines Verifier is a specialized Claude skill designed to automate code compliance and quality assurance within modular or monorepo environments. By enforcing rules defined in localized AGENTS.md files, it automatically groups changed files by scope, applies formatting fixes, executes relevant linting and tests, and generates detailed compliance reports. This ensures that every contribution adheres to project-specific standards, significantly reducing manual review overhead and maintaining high architectural integrity.

Use Cases

  • Monorepo Governance: Automatically identify and apply different linting and testing rules for various modules within a single repository based on the nearest-scoped AGENTS.md configuration.
  • Pre-Review Quality Gate: Streamline the development workflow by auto-fixing formatting issues and catching linting errors locally before code is submitted for human review.
  • Automated Compliance Reporting: Generate structured reports that highlight rule violations and missing documentation, providing developers with actionable feedback to ensure code meets project standards.
  • Change-Based Validation: Optimize productivity by focusing verification efforts only on changed files (staged, unstaged, or untracked), ensuring fast feedback loops during the coding process.
namecoding-guidelines-verify
description"Verify changes follow nearest-scoped AGENTS.md rules: group changed files by nested scope, auto-fix formatting, run lint/tests, and report violations."

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 AGENTS.md is the source of truth for that scope

Workflow (checklist)

  1. Collect changed files (staged + unstaged + untracked).
  2. For each changed file, find the nearest parent AGENTS.md.
    • If a file has no scoped AGENTS.md, report it (suggest running coding-guidelines-gen).
  3. Parse the codex-guidelines block (schema: references/verifiable-block.md).
  4. Run, per scope:
    • format (auto-fix) -> lint -> tests
    • apply simple forbid rules (globs/regex) from the block
  5. Produce a short compliance report (template: references/report-template.md).

Automation

Use scripts/verify_guidelines.py to group scopes, run commands, and report results.