Get Better at Claude Code with One Simple Command

Claude Code has many commands, most of them hidden from the user, and a few not very useful. Today I show you one of the most useful ones: /insights. It analyzes your recent sessions and hands you a report that tells you exactly what to change in your setup to get the best experience possible. One command, one report, and a weekly habit that keeps making Claude Code better for you.

What you need

• Claude Code on the desktop application, the terminal, or the extension
• A few days of real usage, since the report is built from your recent chat sessions

1. What /insights analyzes (0:21)

Insights creates a report that takes into account all of the chat sessions you had with Claude Code within the last three days. It then turns that history into actionable insights you can implement to improve your experience.

This matters because Claude Code has many ways of being customized: the Claude.md file, hooks, custom commands and skills. With that many options, it is very hard to nail the personalization on your first try. The report closes that gap using your own real usage as the evidence.

2. Running the command (0:39)

The only thing you have to do is type:

/insights

It comes pre-installed in Claude Code, so there is nothing to add. Send it, and Claude Code analyzes all of your sessions and comes back with the report.

Generating it usually takes a couple of seconds to a few minutes, depending on how advanced a user you are and on the reasoning level of the model you use. In my case I was running Opus 4.8 on the high setting, and it took about a minute.

Because we are using AI, you do not even have to hunt for the file afterwards. I simply ask Claude to open the report, and we look at it together.

3. The at-a-glance section (1:54)

The report opens with an at-a-glance section that tells you how you currently operate with Claude Code. It covers what is working, what is hindering you, the quick wins you have available, and the most ambitious workflows, the ones you would probably be setting up over the next few months.

From there, you click on whichever section you want and it tells you exactly what to do.

4. The specific problems it found in my setup (2:22)

In my case, the analysis surfaced three concrete issues: some of the scripts I create with Claude Code have errors, Claude Code gives some memory-based answers that it is not verifying, and my workflows are hitting limits.

Then, in the Claude.md suggestions, it tells me exactly what to put inside that file to change this behavior. You have two ways to apply the recommendations: copy the suggestions and paste them manually into your Claude.md, or simply ask Claude Code to read the entire report with you and make the modifications one by one.

5. Suggested skills, MCP servers and future workflows (2:54)

The report goes beyond fixes. It lists custom skills I could create and MCP servers I should install, because Claude Code detected software I am using without the matching integration. In my case that was Notion: I use it, but I did not have the MCP server for it yet.

It also details how I could start using Claude Code for other types of use cases. That part is more for the future. Even if you stop at the fixes, just reading this report tells you exactly what to do about the problems in the use cases you are treating right now.

6. Make it a weekly habit (3:32)

I personally run /insights once a week. That way there is enough data in the last sessions for the report to have some real meat to read through.

Do not bother doing this every single day, unless you are a very new beginner who wants tight guardrails while learning. Weekly is the sweet spot: enough history to find patterns, frequent enough to keep compounding improvements.

Tips

• Let Claude apply the report. Asking Claude Code to read the report alongside you and implement the changes is faster and less error prone than copying by hand.
• Pay attention to the MCP suggestions. They come from software Claude Code actually detected in your sessions, so they are grounded in your real workflow.
• Treat the ambitious workflows section as a roadmap, not a to-do list for today.

Where to go next

Once your setup is tuned, put it to work on long autonomous runs with Make Claude Code Work for Hours. And when you need to share what those sessions produce with your team, see Claude Code Artifacts Explained in 3 Minutes.