The Rundown

In this guide you will learn how to use the Claude Code “insights” feature to improve your coding habits. This hidden, built-in report gives you feedback directly from Claude Code. It will even build you custom skills and agent instructions!

Who This Is Useful For

• Vibe coders who aren’t confident in their coding habits
• Anyone curious what Claude Code thinks of their process
• Data nerds interested in what tools and skills their Claude Code uses the most

What You Will Build

What You Need to Get Started

• Claude Pro or higher subscription
• A computer with the Claude CLI installed
• At least a few weeks of Claude Code usage (more history = better report)
• A code editor (Cursor, VS Code, or just your terminal)

Step 1

Create an empty folder and open it in your IDE (we are using Cursor). Open a new terminal session. Run the command claude /insights.

Pro tip: If this command fails, close Claude Code with ctrl + c and reopen it again. This should update Claude Code. You may have needed an update to use /insights.

Step 2

Claude should begin working on your insights report. When it’s done, it will give you a link to a file named report.html. Copy it into your current folder.

Start the webpage with cmd + shift + p and find the “Open Live Server” tool.

💡Pro tip: you can also give the html to Claude or ChatGPT and have them run it for you.

Step 3

Scroll through the report sections. Here's some of what you'll find:

What You Work On shows cards for each project you've used Claude Code on, with session counts and a summary of what happened. It also breaks down what you asked for most, which tools Claude used, what languages you work in, and your session types.

Impressive Things You Did highlights what went well across your sessions.

Where Things Go Wrong helps you learn where the disconnects are between you and Claude Code.. It flags patterns like Claude ignoring your instructions, producing buggy code, or taking wrong approaches.

Step 4

Now the actionable part. Scroll down to Existing CC Features to Try. This section has copy-paste-ready lines for your CLAUDE.md.

Each suggestion comes with a "Copy" button and an explanation of why it matters for you specifically. For example, if Claude keeps ignoring your theme preferences, you'll see a CLAUDE.md line that says something like:

This project uses TypeScript with a custom shadcn/ui dark theme. ALWAYS use the initialized theme tokens instead of arbitrary Tailwind color classes.

Open your CLAUDE.md in any project, paste these in, and Claude will follow them in every future session.

Step 5

The report also suggests Custom Skills and Hooks based on your patterns.

Custom skills are reusable prompts you trigger with a single command. If you keep doing the same task over and over (like generating CLAUDE.md files for new repos), the report will suggest turning that into a skill so it runs with one command instead of a full session.

To set one up, just paste the skill code from the report into Claude Code and say:

Set up this skill

Claude creates it for you. Now you can use it anytime with a custom slash command in Claude Code.

💡Pro tip: To use newly installed skills you need to exit and restart Claude Code.

Going Further

Run /insights once a month. As your habits (hopefully) improve, Claude Code will surface new skills and instructions you can use. Sometimes feedback is project specific so if you’ve been struggling with a project all month, this is a good way to get feedback.