Non-Copilot customization file detection#304
Open
FokkoVeegens wants to merge 7 commits intorajbos:mainfrom
Open
Non-Copilot customization file detection#304FokkoVeegens wants to merge 7 commits intorajbos:mainfrom
FokkoVeegens wants to merge 7 commits intorajbos:mainfrom
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This PR adds “missed potential” detection to the Usage Analysis dashboard by identifying workspaces that contain non-Copilot AI tool instruction/config files (e.g., Cursor/Windsurf/Claude) but have no Copilot customization files, and then surfacing those workspaces in the UI.
Changes:
- Extends customization scanning to tag discovered files with a
category(copilotvsnon-copilot) and computes amissedPotentialworkspace list in usage analysis stats. - Updates the Usage Analysis webview to render a new “Missed Potential” section/table.
- Expands
customizationPatterns.jsonwith non-Copilot detection patterns and adds a design/spec document.
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 4 comments.
| File | Description |
|---|---|
| src/extension.ts | Adds category propagation during scanning, computes missedPotential, and includes it in stats sent to the Usage Analysis webview. |
| src/webview/usage/main.ts | Adds types and UI rendering for the new “Missed Potential” section. |
| src/customizationPatterns.json | Introduces category for existing patterns and adds non-Copilot tool patterns. |
| docs/specs/nonCopilotFilesDetection.md | Adds a design/spec describing goals, detection approach, and UI behavior. |
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request introduces detection and reporting of "missed potential" workspaces—repositories that contain AI instruction/config files for other tools (like Cursor, Windsurf, Claude, etc.) but lack any Copilot customization files. The goal is to help identify opportunities to encourage Copilot adoption by surfacing these cases in the Usage Analysis dashboard. The implementation involves updates to file scanning patterns, data models, and the UI, as well as new documentation and testing guidance.
Key changes:
Non-Copilot File Detection & Patterns
customizationPatterns.json, each with acategory: "non-copilot"field and relevant metadata (tool name, icon, path, scan mode, etc.). All existing Copilot patterns are now explicitly marked withcategory: "copilot". [1] [2] [3] [4] [5] [6] [7]Data Model & Interface Updates
CustomizationFileEntryinterface to include an optionalcategoryfield ('copilot' | 'non-copilot').MissedPotentialWorkspaceinterface to represent workspaces with non-Copilot files but no Copilot files, and updatedUsageAnalysisStatsto include an optionalmissedPotentialarray.Scanning & Categorization Logic
scanWorkspaceCustomizationFiles()to attach thecategoryfrom the pattern to each discovered file entry. [1] [2]Design & Documentation
docs/specs/nonCopilotFilesDetection.md) detailing the motivation, requirements, implementation plan, file patterns, UI/UX, and verification steps for this feature.These changes lay the groundwork for surfacing "missed potential" workspaces in the dashboard and make it easy to extend detection to new tools in the future.