Allow per-project skill path exclusion (or per-skill disable) for monorepos with non-Next.js apps
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 287
- Forks
- 58
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 17
Description
In a monorepo where one app is Next.js (apps/web/) and another is Expo / React Native (apps/mobile/), the nextjs and next-cache-components skills produce false-positive PostToolUse suggestions on every mobile-file edit, because their pathPatterns are wide enough to swallow both apps.
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
Start by locating the skill pathPatterns and PostToolUse suggestion handling in the TypeScript plugin. Define how per-project path exclusions or per-skill disabling should be configured, then verify that edits under apps/mobile/ no longer trigger the nextjs or next-cache-components skills while apps/web/ still does.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100