Framework detection: move to LLM-based detection + monorepo handling
Open
Nobody has claimed this yet.
P2
wizard-pain
- Dominant language
- TypeScript
- Stars
- 197
- Forks
- 51
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 94
Description
Framework detection is still painful, especially in monorepos.
Raw notes from triage:
- Move entirely to LLM detection and haiku?
- Monorepos are kicking our butts still
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by locating the current framework-detection flow and its monorepo handling, then clarify whether the goal is fully LLM-based detection and whether Haiku is required. Done should mean framework detection works reliably for monorepos under an agreed design.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100