align-repo

Audit CLAUDE.md and .claude/settings.json for team standard alignment.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/kagenti/humr --skill align-repo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: align-repo
Source: https://github.com/kagenti/humr/tree/main/.agents/skills/align-repo
Command: npx skills add https://github.com/kagenti/humr --skill align-repo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit the repository's CLAUDE-related configuration to ensure alignment with team standards.

Core Features & Use Cases

  • Checks presence and structure of CLAUDE.md and .claude/settings.json.
  • Validates attribution blocks, allowed tools, worktrees conventions, and commit standards.
  • Provides actionable gaps and remediation steps for new or existing projects.

Quick Start

Run the alignment audit against the repository to verify CLAUDE configuration and conventions.

Frequently Asked Questions about align-repo

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

FAQPage Schema
How do I validate CLAUDE.md and settings.json configuration in my repository?

Repository CLAUDE configuration audits check the presence and structure of CLAUDE.md and .claude/settings.json against team standards, then report gaps with actionable remediation steps for new or existing projects.

What is the best way to standardize attribution and commit conventions across multiple repos?

Standardizing attribution and commit conventions across repositories involves running an alignment audit that validates allowed tools, worktrees conventions, and commit standards in your CLAUDE configuration, then applying the provided remediation steps.

Can I check worktrees conventions and allowed tools in .claude/settings.json?

Yes, you can check worktrees conventions and allowed tools by auditing .claude/settings.json to validate its structure and contents against your team's defined standards, which identifies any missing or non-compliant configuration entries.

Does this repo alignment audit work for existing projects or only new ones?

The repo alignment audit works for both new and existing projects, validating CLAUDE.md and .claude/settings.json configurations and providing remediation steps to fix any detected gaps regardless of project maturity.

Why does my repository alignment audit report missing CLAUDE configuration gaps?

Repository alignment audits report missing CLAUDE configuration gaps when they detect the absence of required files like CLAUDE.md and .claude/settings.json, or when existing files lack the expected structure for attribution, worktrees, and commit standards.