🔍 How I use /insights to improve my interactions with Claude Code

🔥

Claude Code is my daily driver for coding, and since it dropped back in Feb, I have been using /insights.

If you've never run it: it's one command.

🧑‍💻You type /insights, wait a few minutes, and it reads your last 30 days of sessions, your prompts and Claude's responses, and saves an interactive report (In HTML) in your global .claude folder.

On PC : C:\Users\YOUR_USERNAME\.claude\usage-data

(Local Dir)

On Mac : ~/.claude/usage-data

(Hidden Home Dir)

🔍Find it, 🖱️click it, 📖read it.

(It will open in you defaulted browser.)

If you don't want to find it, once it generates, just ask Claude Code to open it for you.

📝 Note: I look at /Insights like I look at any other advice; I apply what resonates and leave the rest.

It only reads the chat history, not your code. Here's what it did for me.

✅ /Insights tells you what you're doing right, the report doesn't only hunt for friction. It leads with what's working, the habits I built that were worth keeping.

Mine pointed to my session handoffs and my scan-before-deploy discipline as things I had right, and that landed as much as the fixes did. It's easy to only notice what's broken. Having your good patterns named back to you tells you what you should protect while you change the rest.

🎁 And it hands you the recommended solutions, not just problems.

(This was the part I didn't see coming.)

It doesn't stop at naming a rough spot. It writes a solution for you. Ready-to-paste in CLAUDE.md rules, suggested skills with the file already drafted, even hook setups and fresh workflows to try.

So, the moment it surfaces a pattern, the next step is sitting right there. By the time I finished reading, half the work of improving my setup was already done. (With a little iteration of course😅)

==============Now for the lessons====👇============

The first thing it taught me was how I really work. (I will admit, at first, I was in a bit of denial, and that's not a river in Egypt as my grandma would say❤️‍🔥.)

💡The first time I ran /insights It showed me I edited far more than I wrote from scratch, which fit, I was refining and verifying way more than I was generating at the time. (I was doing a lot manually)

💡 Then it surfaced patterns I'd gone blind to. Claude kept reaching for PowerShell (not installed in my VS-Code) when my machine only allowed for Bash.

💡 My styling changes kept drifting from desktop into mobile. None of it was dramatic, but I lived with it for weeks without noticing, and seeing it laid out was the first step to fixing it.

✅ I started researching /Insights and found that the most common mistake people make is stopping there. You read the report, nod, and close the tab.

💡But it's read-only, so if that's where you stop, nothing changes.

Everything I got out of it came from what I did next. Two things, really.

🧠 I learned to turn patterns into rules:

Each thing it surfaced became a line in my CLAUDE.md The PowerShell pattern became a simple rule: this machine has no PowerShell, use Bash only.

The styling one became a rule to scope every change to the right breakpoint and to move things rather than squish them. Now they're handled from the first message of the next session, because I fixed them at the source instead of relearning them every day.

🛠️ I learned to turn rituals into skills, which I recently wrote a post about.

(You can read it here)

💡 It also showed me how much of my work is the same steps over and over.

The clearest one is how I close out a session: update my handoff doc, verify the actual commit hash, run my checks, push to origin.

✅ Once I saw it written down as a pattern, packaging it was obvious. I turned it into a /handoff skill, and now wrapping up is one command instead of walking through it by hand every time. I

🔁 Why I keep running it:

This is what changed how I think about working with Claude Code. Fixing one bad answer fixes that answer. Turning the lesson into a rule or a skill fixes every answer after it.

💡I stopped patching symptoms and started improving the source. So, I run /insights between once and twice a month, sit with what it surfaces, and turn the top couple of things into a rule or a skill. The setup gets a little sharper each pass, and it adds up.

📝 Note: /Insights actually gives you helpful suggestions and yes, it even builds the skills to combat the unseen friction within your interactions with Claude Code.

If you run it, I'd love to hear what yours taught you about the way you work.

Mine showed me more than I expected.

📚 Want the full list of commands? It's all in the Claude Code docs: https://code.claude.com/docs/en/commands

Do you use / commands?

I did not know about /insights

I knew about /insights but have not used it

I knew about /insights and I use it all the time

17 votes

38 comments