project-standards-reviewer

Audits changed files against CLAUDE.md and AGENTS.md standards, citing exact rule violations.

434|33|Updated Jul 27, 2025
One-click install
npx skills add https://github.com/udecode/kitcn --skill project-standards-reviewer-udecode
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-standards-reviewer
Source: https://github.com/udecode/kitcn/tree/main/.agents/skills/project-standards-reviewer
Command: npx skills add https://github.com/udecode/kitcn --skill project-standards-reviewer-udecode

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Always-on code-review persona audits changes against the project's CLAUDE.md and AGENTS.md standards to ensure frontmatter rules, reference inclusion, naming conventions, cross-platform portability, and tool selection policies are followed.

Core Features & Use Cases

  • Automated standards evaluation: compares diffs against CLAUDE.md and AGENTS.md criteria.
  • Enforces reference/directive usage and consistent naming conventions across files.
  • Cross-platform portability checks and tool-selection policy enforcement during reviews.

Quick Start

Run the project standards reviewer on your latest changes to validate compliance with CLAUDE.md and AGENTS.md and surface 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 automate code reviews against CLAUDE.md and AGENTS.md standards?

Automate code reviews against CLAUDE.md and AGENTS.md standards by auditing changed files to identify frontmatter, reference, naming, portability, and tool-selection violations with exact rule citations.

What is standards-compliant code review for project configuration files?

Standards-compliant code review for project configuration files evaluates your diffs against defined criteria, enforcing reference usage, naming conventions, and cross-platform portability policies during the review process.

How do I check cross-platform portability and tool-selection policies in a code review?

Check cross-platform portability and tool-selection policies in a code review by applying an audit across all changed repository files, comparing changes against your standards to surface violations.

Can I enforce frontmatter compliance and naming conventions across all changed files?

You can enforce frontmatter compliance and naming conventions across all changed files by running an automated audit that reads your standards files and flags every violation with the exact rule section.

Does the standards audit cite the exact rule and section for every finding?

Yes, the standards audit reads each relevant standards file and cites the exact rule and section for every finding, ensuring every identified violation traces back to a specific policy.

What are the limitations of automated standards evaluation for code changes?

Automated standards evaluation for code changes is limited to the rules defined within your CLAUDE.md and AGENTS.md files, focusing strictly on frontmatter, references, naming, portability, and tool selection.