Claude Code's /insight command analyzes developer workflow patterns from real usage data

What Claude Code's /insight command found

Claude Code recently added a /insight command that analyzes your usage patterns. One developer used it after 22 days of building a personal finance iOS app, generating a detailed report on their workflow.

Raw usage statistics

• 529 messages across 47 sessions
• 47,604 lines of code added
• 632 files touched
• 146 commits
• Average: 24 messages per day, about 7 hours per session

What worked well

The report identified an effective pattern the developer calls an "audit-then-batch-fix pipeline":

• Ask Claude to do a deep audit of a screen (typically finding 55-73 issues)
• Fix issues in numbered batches
• Commit and deploy after each batch
• Built two complete apps from scratch through incremental prompts with zero TypeScript errors at the end

What cost time

• Claude's first fix attempt frequently misses the root cause, leading to 3-4 round debugging loops
• One navigation bug took 15+ attempts across multiple sessions
• Longest sessions (20+ hours, 200+ files changed) had the highest friction rates
• Claude loses coherence in extended sessions, leading to incomplete work

Recommendations from the report

• Force systematic debugging with console.logs after one failed attempt instead of letting Claude keep guessing
• Add pre-commit hooks that automatically run TypeScript checking and ESLint before every commit
• Shorter focused sessions with clear batch scope have much better outcomes

Additional stats from the report

• 45 feature implementations
• 37 bug fixes
• 16 UI redesigns
• 14 deployments
• Primary friction types: buggy code (28 instances) and wrong approach (25 instances)
• Satisfaction: "likely satisfied" for 139 out of 198 rated interactions

The developer notes that the /insight command is "basically a performance review of your AI collaboration patterns" and that implementing the suggestions could save hours per week.