Copilot instruction udpates - Issue Analysis and Plan of Action #36351
Description
Create GitHub Copilot instruction for the aspnetcore.docs repo that provides a issue analyisis and plan of action report in the issue chat.
If that is approved with stakholders, move to automation so that it runs on each new issues.
GitHub Issue Analysis and Plan of Action Prompt - Summary
- Guides an AI or human reviewer through a structured analysis of GitHub documentation issues.
- Ensures all relevant context is gathered: issue content, comments, documentation source, linked references, and environment details. Github copilot currently does not chase down all of these these details before creating a PR.
- Validates whether an issue is actionable for documentation (not product bugs, sufficient info, correct .NET version).
- Directs reviewers to exact source file lines/sections needing change, with GitHub permalinks and quoted content.
- Recommends documentation improvements as clear, actionable steps (edits, blocks, code samples).
- Encourages precise change tracking: what, where, why, and how, including warnings or notes for breaking changes.
- Translates any non-English content in the issue to help revieweers.
- Output is a Markdown report ready for posting in GitHub issue discussion for transparency and traceability.
- Promotes consistency and completeness in ASP.NET Core documentation issue triage and resolution.
Possible location:
.github/copilot/issue-analysis-action-plan.md
The analysis/action plan needs to run on all new issues (not just Blazor), so I guess we would want to keep responsibilities separated form the existing Blazor workflow yaml for new issues, so create a new workflow (e.g., .github/workflows/issue-analysis.yml) with on: issues: types: [opened].