project-standards-reviewer

Audit code changes against CLAUDE.md and AGENTS.md standards with exact rule citations.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/Andreicr1/netz-analysis-engine --skill project-standards-reviewer-andreicr1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-standards-reviewer
Source: https://github.com/Andreicr1/netz-analysis-engine/tree/main/.gemini/skills/project-standards-reviewer
Command: npx skills add https://github.com/Andreicr1/netz-analysis-engine --skill project-standards-reviewer-andreicr1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audits changes against the project's CLAUDE.md and AGENTS.md standards to detect violations early and ensure consistent rule enforcement across the codebase.

Core Features & Use Cases

  • Enforces reference inclusion, naming conventions, and frontmatter rules across changes.
  • Validates cross-file portability and tool-selection policies to maintain project compatibility.
  • Reports violations with exact rule citations drawn from CLAUDE.md and AGENTS.md.

Quick Start

Run an on-demand audit for a given set of changed files against the repository's CLAUDE.md and AGENTS.md standards and report violations with exact rule citations.

Frequently Asked Questions about project-standards-reviewer

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

FAQPage Schema
How do I audit code changes against CLAUDE.md and AGENTS.md standards?

To audit code changes against CLAUDE.md and AGENTS.md standards, run an on-demand review that traverses ancestor directories to locate configuration files, applies their criteria to changed files, and reports verifiable violations with exact rule citations.

How does code review citation ensure compliance with project standards?

Code review citation ensures compliance by resolving applicable standards from CLAUDE.md and AGENTS.md files, validating cross-file portability and naming conventions, and returning only verifiable violations with precise rule references to avoid irrelevant guidance.

Can I enforce naming conventions and frontmatter rules across changed files?

Yes, you can enforce naming conventions and frontmatter rules across changed files by auditing them against the repository's CLAUDE.md and AGENTS.md standards, which validates reference inclusion and tool-selection policies to maintain project compatibility.

What is the best way to detect standards violations early in a codebase?

The best way to detect standards violations early is to audit code changes against CLAUDE.md and AGENTS.md standards, ensuring consistent rule enforcement across the codebase by reporting violations with exact rule citations drawn from the configuration files.

Does the audit work with cross-platform compatibility in mind?

Yes, the audit works with cross-platform compatibility in mind by validating cross-file portability and tool-selection policies, resolving applicable standards from ancestor directories, and keeping compatibility constraints central when reporting verifiable violations.