The /insights Command: A Full Report on How You Use Claude Code

Claude Code now has a built-in /insights command that generates a full usage report. It tells you what you work on, where things go wrong, and gives you copy-paste suggestions for custom skills and hooks based on your actual workflows.

What the Report Shows

Run /insights and you get a structured report covering your entire Claude Code usage history. The report includes:

Message count and code volume. In the example shown, the user had sent 22,498 messages, generated or modified between +837,350 and -174,481 lines of code, across 9,090 files, over 37 days, averaging 608.1 messages per day.
What you primarily work on. The report breaks this down by category. In the demo, the top categories were Code Refactoring and Deduplication, Git Workflow and Commit Management, and Bug Fixes and Issue Resolution.

Insights report showing usage statistics: 22,498 messages, 837K lines added, 9,090 files, 37 days, and breakdown of work categories including code refactoring and git workflow

Where things go wrong. The report identifies recurring failure patterns so you can address the root causes.

Custom Skills and Hooks Suggestions

The most useful part of the report is the suggestions section. Based on your usage patterns, /insights generates ready-made custom skills, hooks, and workflow ideas that you can copy and paste directly into your configuration.

Insights report section showing suggested custom skills including reusable bisect/git commands, commit message enforcement, and hooks for running type checks and linting automatically

For example, if the report sees that you spend a lot of time on commit message formatting, it might suggest a custom Git commit hook that enforces your exact format rules automatically. If it notices you repeatedly refactor the same patterns, it could suggest a skill that handles those refactoring operations in one command.

How to Run It

Type /insights in your Claude Code session. The report saves to your .claude/usage directory and is immediately available to review. You can drill into any section for more detail.

Terminal showing the /insights command being run, with the insights report file path and a prompt to explore sections

Key Takeaways

/insights generates a full usage report covering message volume, code output, work categories, and failure patterns
The report suggests custom skills and hooks tailored to your specific workflows
The suggestions are copy-paste ready, so you can immediately start automating your most common patterns