WHAT IS CLAUDE insights? The /insights command in Claude Code generates an HTML report analysing your usage patterns across all your Claude Code sessions. It’s designed to help us understand how we interact with Claude, what’s working well, where friction occurs, and how to improve our workflows. From my insights report (new WSL environment, so only past 28 days): Your 106 hours across 64 sessions reveal a power user pushing Claude Code hard on full-stack bug fixing and feature delivery, but with significant friction from wrong approaches and buggy code that autonomous, test-driven workflows could dramatically reduce. Below are the practical improvements I made to my AI Workflow (claude.md, prompts, skills, hooks) based on the insights report. None of this prevents Claude from being wrong. It just makes the wrongness faster to catch and cheaper to fix. CLAUDE.md ADDITIONS Read before fixing Check the whole stack Run preflight on every change Multi-layer context Deep pass by default for debugging Don’t blindly apply external feedback CUSTOM SKILLS /review /preflight PROMPT TEMPLATES Diagnosis-first debugging Completeness checklists Copilot triage ON THE HORIZON - stuff the report suggested that I haven’t fully implemented yet. Autonomous bug fixing Parallel agents for full-stack features Deep audits with self-verification I’m curious what others found useful in their insights reports? submitted by /u/BlunderGOAT
Originally posted by u/BlunderGOAT on r/ClaudeCode
You must log in or # to comment.