VeryGoodOpenSource / VeryGoodOpenSource/vgv-wingspan
chore: Collect usage insights to improve plugin quality
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 105
- Forks
- 15
- Avg merge
- 13h 12m
- Merged PRs (30d)
- 2
Description
Description
Currently, plugin improvements are driven by explicit bug reports or feature requests. However, many pain points go unreported. By collecting aggregated, anonymized insights — such as which review types are most used, common prompt patterns, and where responses are frequently retried or dismissed — we can:
- Identify the most impactful areas to improve
- Spot recurring patterns that suggest missing review categories
- Prioritize fixes based on actual usage, not assumptions
There are two ways to do that i see right now
- Retrieve
/insightsmanually from users - Add
/insightscommand as part of workflow and report it somewhere automatically (after opt-in)
Requirements
No response
Additional Context
No response
Contributor guide
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 comparing the two proposed approaches: manually retrieving /insights or adding an opt-in /insights command to the workflow. Define what aggregated, anonymized insights should include and where automatic reporting would go; done means one agreed implementation path with clear privacy and usage boundaries.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- analytics, cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100