coding-guidelines-verify

Verify code changes against nearest AGENTS.md guidelines with autofix, lint, and tests.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Nymbo/Skills --skill coding-guidelines-verify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coding-guidelines-verify
Source: https://github.com/Nymbo/Skills/tree/main/coding-guidelines-verify
Command: npx skills add https://github.com/Nymbo/Skills --skill coding-guidelines-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Verifies that changes follow the nearest-scoped AGENTS.md rules, groups changed files by their nested scope, auto-fixes formatting, and runs lint/tests with a concise violations report. Designed for monorepos where scope is determined by AGENTS.md location.

Core Features & Use Cases

  • Scope-aware verification: Clusters changed files by their nearest AGENTS.md and enforces per-scope rules.
  • Automation pipeline: Auto-fixes formatting, runs lint/tests, and reports violations.
  • Monorepo readiness: Each module's AGENTS.md is treated as the authoritative scope.

Quick Start

Use the verifier to scan changes:

  • python coding-guidelines-verify/scripts/verify_guidelines.py

Frequently Asked Questions about coding-guidelines-verify

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify code changes against nested AGENTS.md guidelines in a monorepo?

Run the verification script to detect and enforce conformance of your code changes to the nearest AGENTS.md codex guidelines. It clusters changed files by scope, auto-fixes formatting, runs lint and tests, applies forbid rules, and produces a compliance report showing violations.

Can I automate compliance checking across multiple modules with different coding standards?

Yes. The verifier handles scope-aware verification by treating each module's AGENTS.md as authoritative, clustering changed files by their nearest scope, and enforcing per-scope rules independently across your monorepo.

What types of changes does the verification process cover?

The verifier handles staging, unstaged, and untracked changes. It detects which files fall under which AGENTS.md scope, runs formatting fixes and lint checks per scope, applies simple forbid rules, and reports violations for each scope separately.

How does the monorepo structure affect guideline enforcement?

Scope is determined by AGENTS.md location within your monorepo. Each nested AGENTS.md block defines the authoritative rules for files in its directory tree, allowing different modules to maintain distinct coding standards while the verifier enforces them consistently.

What output does the verification script produce?

A concise compliance report that groups violations by scope, shows which auto-fixes were applied, reports lint and test results, and clearly indicates which forbid rules were violated and in which module scopes.

Do I need to set up special tooling before running the verifier?

The verifier requires AGENTS.md files to exist in your monorepo structure. Beyond that, it automates the pipeline—extracting codex-guidelines blocks, running formatting, lint, and tests—so you don't need to invoke each tool separately.