Allow /insights to be scoped to a specific project or repo
Preflight Checklist
- [x] I have searched existing requests and this feature hasn't been requested yet
- [x] This is a single feature request (not multiple features)
Problem Statement
I found the /insights tool really useful.
BUT insights can not be scoped to a specific project and it limits its utility.
Proposed Solution
Allow insights to provide a report scoped to one specific project or repo.
Alternative Solutions
Not available
Priority
Low - Nice to have
Feature Category
CLI commands and flags
Use Case Example
I work across multiple projects and in some cases want to see friction patterns and suggestions per-project, not just globally.
For example, the patterns I follow in UI are different from the ones for the backend. Because I develop the backend on a VM and the UI on a different desktop, I was able to separate them. But that doesn't work when working on different projects on the same desktop.
For example, the desktop report (mostly UI development):
▎ What's working: You've built a strong workflow using Claude as an iterative design partner for SvelteKit — driving complex UI features like expandable grids and sandboxed JS execution to completion through persistent feedback loops. Your research-to-implementation pipeline is also effective, turning broad FP and market research into concrete convention docs and utility libraries. Impressive Things You Did →
And the backend VM report:
▎ What's working: You have a strong multi-repo, multi-language workflow — jumping between TypeScript, SQL, Perl, and PowerShell in single sessions to fix bugs and ship features across your qualify ecosystem. Your discipline around documentation (MEMO, CHANGELOG, dated entries) and integration testing means you're building durable project knowledge alongside the code, not just patching things. Impressive Things You Did →
Note that in my desktop I have much more variation acrosss projects, so more specific insights would be welcomed.
Additional Context
_No response_
This issue has 5 comments on GitHub. Read the full discussion on GitHub ↗