claude-code - 💡(How to fix) Fix /insights: per-project recommendations instead of mixing everything together [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#48451Fetched 2026-04-16 06:59:47
View on GitHub
Comments
0
Participants
1
Timeline
2
Reactions
0
Author
Participants
Timeline (top)
labeled ×2
RAW_BUFFERClick to expand / collapse

Hey! Love the /insights feature, spent some time reading through my report and there's genuinely useful stuff in there.

One thing though. I work across several very different projects. One is pure Bash scripts with some Python, another is Java/Spring Boot with Oracle, another has no Spring at all. The report mixes all sessions together and gives recommendations that assume everything is the same stack.

For example it suggested adding mvn compile as a post-edit hook and described my project as "Java/Spring Boot with Oracle". That's true for one project but makes zero sense for my VPN infra repo that's all shell scripts. Same with the CLAUDE.md suggestions, they're written as universal rules but really only apply to one of my projects.

What I'd actually want is something like this. It can still be one report, that's totally fine, but the recommendations should work on two levels. If there's a pattern across all my projects (like "don't add Co-Authored-By" or "prefer simpler approaches") then show it as a global thing and maybe suggest how to set it up globally in settings or global CLAUDE.md. But if something is specific to one project's stack then just say so. Like "for your Java/Spring project add this hook" instead of just "add this hook" as if I only have one project.

The data is already there since sessions are tied to working directories. It's just the analysis part that blends everything into one.

extent analysis

TL;DR

The issue can be addressed by modifying the analysis to differentiate between project-specific and global recommendations based on the working directory and project stack.

Guidance

  • Identify the unique characteristics of each project, such as programming languages and frameworks used, to determine the scope of recommendations.
  • Modify the analysis to group recommendations by project or stack, rather than providing a single set of recommendations that applies to all projects.
  • Consider adding a project-specific filtering or categorization mechanism to the report generation process to ensure that recommendations are relevant to each project.
  • Review the current report generation logic to determine how it can be updated to handle multiple projects with different stacks.

Example

No code snippet is provided as the issue does not contain specific code examples.

Notes

The solution may require updates to the report generation logic and analysis algorithms to handle multiple projects with different stacks. The exact implementation details will depend on the current architecture and technology stack of the reporting tool.

Recommendation

Apply a workaround by modifying the analysis to provide project-specific recommendations, as upgrading to a fixed version is not mentioned in the issue. This approach will allow for more accurate and relevant recommendations for each project.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING