Claude Code /insights: Find Inefficiencies in Your Work Pattern Report

You work hard, but sometimes wonder "am I actually using Claude Code well?" It's vague where you spend the most time or where you keep getting stuck. The command that shows this as data rather than gut feeling is /insights.

Definition (What It Is)

/insights is a command that analyzes how you've been using Claude Code and turns that usage pattern into a report.

"Insights" can be rendered roughly as "perceptions," but here it means "meaningful information extracted from your work data." It organizes and shows things like which tasks you do often, which areas you touch a lot, and where you frequently stall.

It's similar to receiving a health checkup result sheet. Habits you usually pass over without noticing get laid out as numbers and items.

How to Use It (By Difficulty)

Basic — Getting the Report

Just type it.

/insights

This displays a report analyzing your usage patterns so far. Items like the areas you handle often and the friction points are laid out.

Intermediate — Checking It Regularly

Rather than looking once and being done, it's better to set a cadence and keep up with it.

/insights

For example, run /insights once a month to check that month's patterns. Comparing with when you first saw it reveals how your work style has changed and whether it has improved.

Advanced — Turning the Report Into Action

A report is meaningless if it ends at just looking. Connect it to the next step.

1. Check friction points (parts where you frequently stall or spend a lot of time) with /insights.
2. Look for a command or habit that would reduce those points.
3. After applying it for a while, check the effect again with /insights.

If you spot "a task you use a lot but that takes a lot of effort each time," that's the top candidate to improve first.

Common Pitfalls

• If there's almost no data, the report is thin too. You need to use Claude Code for a while before meaningful patterns appear.
• The report is a diagnosis, not a prescription. It only tells you "you spend a lot of time here" — how to change it is up to you to decide.

Real-World Example

A beginner developer ran /insights after using Claude Code for about a month. The report revealed they were spending a lot of time explaining similar setup tasks from scratch each time. So they switched to organizing frequently used instructions separately and reusing them — and next month's report showed that friction point noticeably reduced.

Taking It Further

Once you've examined your usage patterns, you can also check usage itself with /usage to see how much you've used. If you work as a team, you can use this report for onboarding new members, sharing "you tend to get stuck here, so know it in advance." /insights works for solo retrospectives and for team improvement alike.

Summary

/insights is a command that organizes and shows your Claude Code usage patterns as data. Its true value comes out when you confirm where you spend time and where you get stuck with numbers rather than gut feeling, and connect that to improving your work style. Pull it out occasionally after you've used it for a while.

Based on: Claude Code v2.1.154 (2026.05)