microsoft / microsoft/vscode-dotnettools
[P1][Tier 2] Provide agent-friendly analyzer/lint/format summaries mapped to file locations
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 321
- Forks
- 54
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 2
Description
Tier 2 — Feedback readiness · Priority: P1
Gap
Analyzers, ESLint/Prettier, and C# analyzers exist, but their output is not packaged as agent-friendly summaries that map diagnostics to file locations and likely fixes.
Investment
- Add structured diagnostics or an agent-friendly analyzer/lint/format summary (file, rule, location, suggested fix).
Acceptance criteria
- Analyzer/lint/format output is available in a form that maps to file locations and likely fixes.
- An agent can consume the summary without manual translation.
Part of epic #3273
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
Review epic #3273 and the existing analyzer, ESLint/Prettier, and C# analyzer outputs first; the issue names no files or tests. The work is complete when diagnostics are exposed as agent-consumable summaries containing file locations, rules, suggested fixes, and no manual translation is needed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, eslint
- Domain
- devtools, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100