conform

Compare changed code against CLAUDE.md and local rule files to report violations.

Updated Mar 6, 2026
One-click install
npx skills add https://github.com/sQVe/cape --skill conform-sqve
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: conform
Source: https://github.com/sQVe/cape/tree/main/skills/conform
Command: npx skills add https://github.com/sQVe/cape --skill conform-sqve

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the enforcement of documented coding conventions by comparing changed code against CLAUDE.md rules and per-language rule files, surfacing violations early.

Core Features & Use Cases

  • Automatically check changed files against CLAUDE.md and local rule files.
  • Produce a structured, file-wide report listing each violation with exact file and line references.
  • Integrate with CI or pre-commit workflows to gate non-compliant changes and maintain code quality.

Quick Start

Run cape conform to evaluate the current workspace for conformance against configured rules.

Frequently Asked Questions about conform

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

FAQPage Schema
How do I automate code convention checks against CLAUDE.md rules?

To automate code convention checks, run the tool to parse CLAUDE.md and local rule files, evaluating changed workspace files to generate a structured report of exact rule violations with file and line references.

Can I check only staged or unstaged files for linting rule violations?

Yes, you can check unstaged or staged files for linting rule violations. The tool evaluates changed files across branch, unstaged, or staged scopes, using globs in rule files to determine which checks apply to each file.

Does this tool work with pre-commit hooks to gate non-compliant code changes?

Yes, it works with pre-commit hooks to gate non-compliant code changes. You can integrate the automated convention checks directly into CI or pre-commit workflows to maintain code quality by blocking violations early.

What is the best way to enforce coding conventions across a git repository?

The best way to enforce coding conventions is to define rules in CLAUDE.md and per-language rule files, then use an automated checker to compare changed repository files against these rules and produce a structured violation report.

How does the rule mapping process determine which conventions apply to a changed file?

The rule mapping process uses globs defined in local rule files to determine applicability. It parses these rules, gathers data on changed files within the current repository scope, and maps the relevant conventions to each file for checking.