Insights: make reports context-aware to avoid repeating already-implemented suggestions

Feature Request

The /insights report is a great tool, but across multiple reports it keeps suggesting things I've already implemented. For example, my latest report suggested:

• Adding YAML lint hooks — already set up in my settings.json
• Creating a Docker status slash command — already exists at .claude/skills/docker-debug/
• Documenting ports in a HOMELAB.md — already handled by a SessionStart hook that auto-populates my CLAUDE.md with a running services table

Since the report is generated from session data but doesn't look at the current project state, it has no way to know what's been done.

Suggestion

Make insights more context-aware and interactive:

1. Diff against current state — Before generating suggestions, explore the project for existing skills, hooks, CLAUDE.md content, and settings so the report can filter out what's already been implemented and focus on fresh, actionable advice.

1. Track previous reports — Know what was suggested last time and whether it was acted on, so each report builds on the last instead of repeating it.

1. Interactive mode — Allow the user to dig deeper into specific sessions or suggestions conversationally, rather than generating a static one-shot report.

The goal is: each time I run /insights, I get genuinely new recommendations rather than having to manually cross-reference against what I've already done.

🤖 Generated with Claude Code