skills.rest
thrawn01
thrawn01COMMUNITY
Explore all skills by this author →
Website𝕏@thrawn01GitHub

review-guidelines

Identify CLAUDE.md guideline violations in git diffs and report them.

11|Updated Sep 5, 2025
Search Tags:#reporting#review#guidelines#code-review#diffs#claude-md
One-click install
npx skills add https://github.com/thrawn01/claude-dotfiles --skill review-guidelines-thrawn01
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-guidelines
Source: https://github.com/thrawn01/claude-dotfiles/tree/main/skills/review-guidelines
Command: npx skills add https://github.com/thrawn01/claude-dotfiles --skill review-guidelines-thrawn01

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review and enforce CLAUDE.md guidelines on code changes, ensuring compliance before merging.

Core Features & Use Cases

  • Change scope detection: determine affected files from diffs.
  • Guideline alignment: compare changes against CLAUDE.md mandates.
  • Report generation: produce structured violation summaries and recommended fixes.

Quick Start

Review the latest diff for the current branch and report any guideline violations.

Frequently Asked Questions about review-guidelines

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

FAQPage Schema
How do I check a git diff for CLAUDE.md guideline violations?▼

You can check a git diff for CLAUDE.md guideline violations by comparing modified files on your current branch against the mandates. It outputs structured violation summaries and recommended fixes while excluding pre-existing issues outside the changed lines.

Can I review code changes against a specific targeted file instead of the whole branch?▼

Yes, you can review code changes against a targeted file. The process detects modified files within a repository using git, allowing you to isolate the scope to a specific file or the entire current branch diff.

Does the code review process report pre-existing violations in unchanged lines?▼

No, the code review process excludes pre-existing issues outside the changed lines. It specifically evaluates and reports code guideline violations found only within the modified lines of a diff compared to CLAUDE.md.

What is the best way to enforce CLAUDE.md compliance before merging code?▼

The best way to enforce CLAUDE.md compliance before merging is to audit code changes from your current branch, align them against the guidelines, and generate structured violation summaries with recommended fixes to resolve deviations.

Do I need git to detect affected files for a CLAUDE.md review?▼

Yes, you need git to detect affected files for a CLAUDE.md review. Change scope detection determines affected files from diffs within a repository using git, focusing exclusively on modified files.

Related Skills

Explore More Software Engineering Skills→
reedomreedom

detect-kiro-specs

Detect modified Kiro specs in the current branch using git diff.

Community
Basic
LonelyHerbivoreLonelyHerbivore
92

check

Validate changed code against .trellis/spec/ guidelines using git diff.

Community
Intermediate
mkusakamkusaka
7

code-review-conventions-dimension

Flag code diff lines violating CLAUDE.md file rules.

Community
Intermediate
Obsidian-OwlObsidian-Owl
9

gate-wiring

Detect unused exports, orphaned files, layer violations, and circular dependencies in changed code.

Official
Intermediate