claude-code-analyzer

Audit Claude Code configuration files, commands, hooks, agents, and MCP settings.

Updated Jul 5, 2026
One-click install
npx skills add https://github.com/zzafergok/tulpar --skill claude-code-analyzer-zzafergok
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: claude-code-analyzer
Source: https://github.com/zzafergok/tulpar/tree/main/.agent/skills/claude-code-analyzer
Command: npx skills add https://github.com/zzafergok/tulpar --skill claude-code-analyzer-zzafergok

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Claude Code setups accumulate scattered instructions across CLAUDE.md files, commands, hooks, agents, skills, and MCP configuration, leading to duplicated rules, conflicting guidance, and wasted context. This Skill audits that configuration and reports concrete findings with remediation steps. ## Core Features & Use Cases - Configuration Inventory: Inspects project and user CLAUDE.md files, commands, agents, skills, hooks, settings, and MCP server declarations within scope. - Structured Review Criteria: Evaluates scope separation, clarity, context cost, portability, safety, maintainability, and evidence-based recommendations. - Migration and Comparison: Maps Claude Code concepts to Codex or other agent platforms, preserving intent and flagging features without equivalents. - Use Case: A team migrating from Claude Code to Codex uses this Skill to inventory their existing setup, identify duplicated instructions, and produce an impact-ranked report before translating configuration. ## Quick Start Audit my Claude Code configuration and report any conflicting or duplicated instructions across my CLAUDE.md files and settings.

Frequently Asked Questions about claude-code-analyzer

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

FAQPage Schema
How do I audit my Claude Code configuration?▼

Run the analyzer against your project and user scopes to inventory CLAUDE.md files, commands, agents, skills, hooks, settings, and MCP declarations. It reports findings ranked by impact with file paths and concrete remediation steps.

How to migrate Claude Code configuration to Codex?▼

The analyzer maps project instructions, reusable skills, tool integrations, invocation rules, and permission boundaries to the destination platform's supported concepts. It preserves intent rather than copying filenames and flags features without an equivalent.

What files does a Claude Code configuration review cover?▼

The review covers project and user CLAUDE.md instructions, commands, agents, skills, hooks, settings, and MCP server declarations with required credentials. Inaccessible scopes are reported rather than assumed.

Does the analyzer modify my Claude Code configuration files?▼

No, the analyzer uses read-only inspection and does not edit configuration unless the user explicitly requests changes. It separates confirmed problems from optional improvements in its report.

When should I not use the Claude Code analyzer?▼

Do not trigger it for ordinary Codex configuration work or general agent setup unrelated to Claude Code. It is intended only when the user explicitly works with Claude Code or asks to migrate or compare its configuration.