fedius01

Ccinspect — Code Quality skill for Claude Code

Code Quality community

Linter & runtime auditor for Claude Code configs — 40+ lint rules, write-blindness, agent-bypass, orphan agents, ghost MCP servers, token economics, session recovery.

How to install Ccinspect

This entry records only its repository, not the path inside it, so there is no exact command to give. Open fedius01/ccinspect and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Ccinspect does

Linter & runtime auditor for Claude Code configs — 40+ lint rules, write-blindness, agent-bypass, orphan agents, ghost MCP servers, token economics, session recovery. Fully offline.

Alternatives in Code Quality

Refactor Claude Md — Refactor CLAUDE.md by extracting sections to dedicated docs with path-scoped rules 1.6k ★
Brooks Debt — Run a Brooks-Lint tech debt assessment 1.5k ★
Session Start — Start a new development session by creating a session file in .claude/sessions/ with the format YYYY-MM-DD-HHM 1.2k ★

README

⚙️ ccinspect

**Claude Code Configuration Inspector**

A CLI tool that inspects, validates, and visualizes Claude Code configurations across all layers (enterprise, user, project-shared, project-local) — and cross-references them against actual runtime behavior.

Scan · Lint · Blame · Audit · History · Diff · Restore · Recover

[![npm](https://img.shields.io/npm/v/ccinspect)](https://www.npmjs.com/package/ccinspect) [![license](https://img.shields.io/npm/l/ccinspect)](./LICENSE) [![tests](https://img.shields.io/badge/tests-1500%2B%20passing-brightgreen)]()

Goal of the project

Provide Claude Code users with full visibility and confidence that their configuration is correct, conflict-free, efficient, and behaving as intended — like a linter + debugger for your Claude Code setup.

The problem it solves

Claude Code has a complex, layered configuration system — settings files, CLAUDE.md memory files, rules, agents, skills, commands, MCP servers, hooks, and plugins — spread across multiple locations with precedence-based merging. As projects grow, it becomes hard to:

Know what's actually in effect after all layers merge
Spot contradictions between levels (e.g., allow at user level, deny at project level)
Detect dead config (rules with globs matching nothing, orphan agents)
Understand token budget impact (how much context is consumed at startup)
Verify that configuration behaves as intended at runtime

Claude Code uses **30+ config files** across **7+ locations** — and when they conflict, debugging is painful.

**ccinspect** fixes that with next capabilities:

🔍 **Discover** — finds every config file across all scopes and shows sizes, tokens, git status 🧹 **Lint** — runs 52 rules catching security gaps, dead references, conflicts, and bloat 📋 **Evidence** — see exactly which lines triggered each detection 🔗 **Blame** — shows the effecti