claude-code-analyzer

Analyze Claude Code history JSONL to extract tool usage and generate configuration recommendations.

3.0k|372|Updated Apr 12, 2012
One-click install
npx skills add https://github.com/nicknisi/dotfiles --skill claude-code-analyzer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: claude-code-analyzer
Source: https://github.com/nicknisi/dotfiles/tree/main/home/.claude/skills/claude-code-analyzer
Command: npx skills add https://github.com/nicknisi/dotfiles --skill claude-code-analyzer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, gh, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Users often struggle to optimize their Claude Code setup, leading to inefficient workflows, missed community resources, and suboptimal configurations. This skill automates the analysis and recommendation process, ensuring your AI assistant works smarter, not harder.

Core Features & Use Cases

  • Usage Analysis: Automatically extracts tool usage, model distribution, and project activity from your Claude Code history to identify optimization opportunities. This means less manual digging and more actionable insights.
  • GitHub Discovery: Finds relevant community skills, agents, and slash commands on GitHub that match your usage patterns, connecting you to proven solutions without endless searching.
  • Project Analysis: Detects your project's tech stack (e.g., Next.js, Vitest) and suggests tailored CLAUDE.md documentation improvements, ensuring your project context is always up-to-date and useful.
  • Use Case: You want to streamline your Claude Code experience. This skill will tell you which tools to auto-allow, suggest new slash commands for repetitive tasks, and even find community-contributed skills to enhance your specific tech stack, letting AI handle the heavy lifting of configuration.

Quick Start

Run a full analysis for your current project

bash scripts/analyze.sh --current-project bash scripts/analyze-claude-md.sh

Frequently Asked Questions about claude-code-analyzer

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

FAQPage Schema
How do I analyze my Claude Code usage patterns and find optimization opportunities?

Usage analysis extracts tool consumption, model distribution, and project activity from your Claude Code history to identify which tools to auto-allow, commands to create, and configurations to adjust for efficiency.

Can I discover community skills and slash commands that match my project's tech stack?

Yes. GitHub discovery finds relevant community-contributed skills, agents, and slash commands that align with your detected tech stack and usage patterns, surfacing proven solutions without manual searching.

What does project analysis do and how does it improve my CLAUDE.md documentation?

Project analysis detects your tech stack—such as Next.js or Vitest—and generates tailored CLAUDE.md content recommendations, ensuring your project context is current and useful for Claude Code interactions.

What input data do I need to run the analyzer?

You need your Claude Code history in JSONL format. The analyzer parses this file to extract tool usage, model distribution, and project structure, then generates settings, configuration files, and documentation suggestions.

Does this work with GitHub-hosted projects and existing Claude Code configurations?

Yes. The analyzer integrates with GitHub via the gh CLI to discover resources and works alongside existing Claude Code setups, generating incremental recommendations without disrupting current configurations.

What are the limits if my project uses uncommon tools or languages?

Detection relies on identifying recognizable tech stacks. If your project uses less common frameworks or custom tooling, recommendations may be limited; GitHub discovery still finds relevant skills based on available project signals.