Claude Code Insights Reports

This directory contains insights reports generated by the /insights command in Claude Code.

Reports

  • report-2026-02-10.html - Full insights report from February 10, 2026
    • 234 sessions analyzed
    • 659 hours of usage
    • 266 commits

Viewing the Reports

The HTML reports are self-contained and can be viewed in several ways:

  1. Locally: Open the HTML file directly in your browser
  2. GitHub: View directly on GitHub (it will render the HTML)
  3. GitHub Pages: If you enable Pages for this repo, the reports will be accessible at:
    • https://nicolasrouanne.github.io/claude/insights/report-2026-02-10.html

Key Insights from Latest Report

The February 10 report identified:

Top Friction Points

  1. Over-engineered solutions - Claude proposes complex implementations when simpler approaches are preferred
  2. Misinterpreting intent - Starting implementation when only a GitHub issue was requested
  3. Unsafe actions without permission - Merging PRs without explicit approval
  1. Never merge PRs without explicit user approval
  2. Default to posting plans as GitHub issues, not implementing
  3. Prefer simple solutions over complex ones
  4. Use restrictive permissions by default
  5. Use ruff for Python, Jest for React Native testing
  6. Always use realistic factory data with Faker, never None

Features to Try

  • Hooks: Auto-lint Python/TypeScript files after edits
  • Custom Skills: Create /merge skill with approval guardrails
  • Headless Mode: Automate common workflows in CI/CD

Raw Data

The raw session data that generated these reports is stored in ~/.claude/usage-data/facets/. Each JSON file represents a session with metadata about goals, friction, tools used, and outcomes.


This site uses Just the Docs, a documentation theme for Jekyll.