guidelines-compliance

Audit code compliance with CLAUDE.md guidelines across repository directories.

28|3|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/oborchers/fractional-cto --skill guidelines-compliance
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: guidelines-compliance
Source: https://github.com/oborchers/fractional-cto/tree/main/pedantic-coder/skills/guidelines-compliance
Command: npx skills add https://github.com/oborchers/fractional-cto --skill guidelines-compliance

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of auditing code against project-specific coding standards defined in CLAUDE.md files, ensuring consistency and adherence to established rules across the repository.

Core Features & Use Cases

  • Automated Auditing: Scans code files and checks them against applicable CLAUDE.md guidelines.
  • Hierarchical Rule Application: Correctly applies rules from root CLAUDE.md down to feature-specific ones.
  • Use Case: When a new feature is developed, use this Skill to verify that all new code adheres to the project's naming conventions, import order, and architectural patterns as defined in the CLAUDE.md files.

Quick Start

Use the guidelines-compliance skill to audit the file src/utils/helpers.py against all applicable CLAUDE.md rules.

Frequently Asked Questions about guidelines-compliance

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

FAQPage Schema
How do I audit code compliance with project-specific CLAUDE.md guidelines?

This Skill audits code compliance by scanning files against applicable CLAUDE.md rules, identifying violations in naming conventions, import ordering, and architectural patterns defined across your repository directory hierarchy.

How are hierarchical coding standards applied when auditing a specific file?

Hierarchical coding standards are applied using a directory walk-up algorithm that aggregates rules from parent directories, ensuring root CLAUDE.md rules apply globally while feature-specific ones apply locally during the code audit.

What types of coding standard violations can automated auditing detect?

Automated auditing detects violations of project-specific coding standards including naming conventions, import ordering rules, and structural architectural patterns defined within your CLAUDE.md files.

Does this code compliance audit work without predefined CLAUDE.md files?

No, this code compliance audit requires predefined CLAUDE.md files to function, as the auditing mechanism relies entirely on parsing and applying the project-specific coding standards defined within them.

What is the best way to verify new feature code adheres to repository coding standards?

The best way to verify new feature code adheres to repository coding standards is running an automated audit that checks new files against the aggregated CLAUDE.md rules from the root directory down to the feature-specific directory.

When should I not use automated CLAUDE.md compliance auditing?

You should not use automated CLAUDE.md compliance auditing if your repository lacks CLAUDE.md files or if your project relies on external configuration formats for defining coding standards and architectural patterns.