From 2d06d748f96fc70e1b003f3518063de7b95254a9 Mon Sep 17 00:00:00 2001 From: wadepickett Date: Thu, 13 Nov 2025 14:42:24 -0800 Subject: [PATCH 1/8] Add Copilot instruction: Issue analysis and action plan --- .../copilot-issue-verification-action-plan.md | 226 ++++++++++++++++++ 1 file changed, 226 insertions(+) create mode 100644 .github/copilot-issue-verification-action-plan.md diff --git a/.github/copilot-issue-verification-action-plan.md b/.github/copilot-issue-verification-action-plan.md new file mode 100644 index 000000000000..062b19ef2b54 --- /dev/null +++ b/.github/copilot-issue-verification-action-plan.md @@ -0,0 +1,226 @@ +# GitHub Issue Analysis and Action Plan Prompt for ASP.NET Core Documentation + +## Goal +Analyze the GitHub issue and provide a **structured report** determining: +1. Whether the issue is valid and actionable +2. The exact documentation changes required (if applicable) +3. A clear action plan that can guide PR creation + +The report should be suitable for posting directly in the issue discussion. + +--- + +## Analysis Steps + +### 1. Information Gathering +Collect and review: +- The **issue title, description, and all comments** +- The **published documentation** (via the provided URL) +- The **source file(s)** in the repository +- Any **linked issues, PRs, or external references** +- **Environment details**: .NET version, tooling versions (VS, VS Code, CLI, EF Core, etc.) +- **Code samples or error messages** mentioned in the issue + +### 1.5 Source File Analysis +When examining source files: +- **Provide direct GitHub permalinks** to specific lines or sections +- **Note exact line numbers** for proposed changes +- **Include line number ranges** in GitHub URLs using `#L-L` format +- **Quote current content** from specific lines before proposing changes +- **Use permalinks with commit SHA** when referencing specific versions + +Example format for file references: +- Single line: `https://github.com/owner/repo/blob/main/file.md#L123` +- Line range: `https://github.com/owner/repo/blob/main/file.md#L123-L145` +- Permalink: `https://github.com/owner/repo/blob//file.md#L123` + +### 2. Validation Criteria +Determine if the issue is: +- **In scope**: Related to ASP.NET Core documentation (not product bugs) +- **Accurate**: The reported problem genuinely exists +- **Clear**: Sufficient information to take action +- **Current**: Applies to supported .NET versions + +### 3. Translation Requirements +If any content is not in English: +- Include the original text in a quote block +- Provide complete English translation +- Label clearly as "Original" and "Translation" + +--- + +## Output Format + +### File Naming +`-analysis-report.md` + +### Report Structure + +#### Header +```markdown +## AI Analysis Report +**Analyzed by:** @ +**Date:** +**Issue:** # +**Model:** GitHub Copilot +--- +``` + +#### For Valid Issues + +```markdown +# Issue Analysis: + +## ✅ Issue Validation +**Status:** Valid and actionable + +## 📋 Issue Summary + + +## 📁 Affected Files +| File | Path | Lines | Section | +|------|------|-------|---------| +| Main article | [`aspnetcore/path/to/file.md`](https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/path/to/file.md#L123-L145) | 123-145 | "Section Heading" | +| Code sample | [`aspnetcore/path/to/sample.cs`](https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/path/to/sample.cs#L45-L67) | 45-67 | `MethodName()` method | + +## 📝 Proposed Changes + +### Documentation Updates +**File:** [`aspnetcore/path/to/file.md`](https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/path/to/file.md#L123-L145) +**Location:** Lines 123-145 (after the paragraph containing "[specific anchor text]") +**Type:** [New paragraph / Note block / Code example / Replacement] + +**Current content (lines 123-125):** +```markdown +[Current text that will be replaced or followed] +``` + +**Proposed change:** +```markdown +[Proposed documentation text here] +``` + +### Code Sample Updates (if applicable) +**File:** [`sample.cs`](https://github.com/dotnet/AspNetCore.Docs/blob/main/path/to/sample.cs#L45-L67) +**Lines:** 45-67 +**Change:** [Add/Modify/Remove] + +**Current code:** +```csharp +// Current code at specified lines +``` + +**Proposed code:** +```csharp +// Proposed code changes +``` + +## 🎯 Action Plan +1. **Edit file:** [`aspnetcore/path/to/file.md`](https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/path/to/file.md) + - Navigate to: [Line 123](https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/path/to/file.md#L123) + - Find section: "Exact Section Heading" + - After text: "last sentence before insertion point" + - Insert: [!NOTE] block with explanation + +2. **Update sample:** [`path/to/sample.cs`](https://github.com/dotnet/AspNetCore.Docs/blob/main/path/to/sample.cs) + - Navigate to: [Lines 45-67](https://github.com/dotnet/AspNetCore.Docs/blob/main/path/to/sample.cs#L45-L67) + - Modify method: `MethodName()` + - Change: Update to use new pattern + +## ⚠️ Considerations +- Verify change applies to .NET [version] +- Check if similar updates needed in related articles +- Consider adding cross-references to [related topic] + +## 🔗 References +- Published article: [URL] +- Related issue: #[number] +- Microsoft Learn docs: [relevant MS docs link] +``` + +#### For Invalid Issues + +```markdown +# Issue Analysis: + +## ❌ Issue Validation +**Status:** Not actionable as is +**Reason:** [Out of scope / Insufficient information / Product issue / Already addressed] + +## 📋 Explanation + + +## 💡 Recommendation +- [Close with explanation] +- [Redirect to appropriate repository] +- [Request additional information] +- [Convert to discussion] + +## 🔗 Alternative Resources +- [Link to relevant documentation] +- [Link to appropriate repository for product issues] +``` + +--- + +## Special Instructions + +### Line Number Guidelines +- **Always inspect the actual source file** to determine accurate line numbers +- **Provide line ranges** rather than single lines when changes affect multiple lines +- **Use GitHub's line highlighting** format in URLs (#L123 for single, #L123-L145 for range) +- **Quote the existing content** at those lines to confirm accuracy +- **Consider context lines** - include a few lines before/after for clarity +- **Update line numbers** if the file has changed since issue creation + +### Content Block Usage +Only recommend using special blocks when truly appropriate, they should not be overused: +- `[!IMPORTANT]`: Security issues, breaking changes, data loss risks +- `[!WARNING]`: Common mistakes, deprecation notices +- `[!NOTE]`: Helpful clarifications, version-specific info +- `[!TIP]`: Best practices, productivity hints + +### Code Samples +- Use appropriate language identifier for syntax highlighting +- Include necessary `using` statements or imports +- Add comments for complex logic +- Ensure samples are complete and runnable + +### Scope Boundaries +**DO:** +- Focus on documentation clarity and accuracy +- Address missing information +- Fix technical inaccuracies +- Improve code samples + +**DON'T:** +- Attempt to fix product bugs through documentation +- Make architectural recommendations +- Add opinions or preferences +- Modify unrelated sections + +## Issue labels +- Upon completion of the report, set the `ai-reviewed-issue-reported-action-plan` label for the issue. + +### Common Issue Types +1. **Missing information**: Add clarifying content +2. **Outdated content**: Update to current version +3. **Broken samples**: Fix or replace code +4. **Unclear instructions**: Rewrite for clarity +5. **Missing prerequisites**: Add setup steps + +--- + +## Quick Decision Tree + +``` +Is this a documentation issue? +├── NO → Redirect to product repo +└── YES → Is the information accurate? + ├── NO → Provide correction + └── YES → Is it clear enough? + ├── NO → Clarify/expand + └── YES → Is it complete? + ├── NO → Add missing info + └── YES → Consider if enhancement improves value +``` \ No newline at end of file From 97252ea7c3920347afd96040beea21db52af1b74 Mon Sep 17 00:00:00 2001 From: wadepickett Date: Thu, 13 Nov 2025 14:48:08 -0800 Subject: [PATCH 2/8] Add top metadata --- .github/copilot-issue-verification-action-plan.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/.github/copilot-issue-verification-action-plan.md b/.github/copilot-issue-verification-action-plan.md index 062b19ef2b54..e4810e5efea4 100644 --- a/.github/copilot-issue-verification-action-plan.md +++ b/.github/copilot-issue-verification-action-plan.md @@ -1,3 +1,9 @@ +--- +author: tdykstra +ms.author: wpickett +ms.date: 11-13-2025 +--- + # GitHub Issue Analysis and Action Plan Prompt for ASP.NET Core Documentation ## Goal From e3b9f62ee3e499828656c1b921bd3943ea23eaf7 Mon Sep 17 00:00:00 2001 From: wadepickett Date: Thu, 13 Nov 2025 15:02:26 -0800 Subject: [PATCH 3/8] Changed to asterisks for all line items --- .../copilot-issue-verification-action-plan.md | 128 +++++++++--------- 1 file changed, 64 insertions(+), 64 deletions(-) diff --git a/.github/copilot-issue-verification-action-plan.md b/.github/copilot-issue-verification-action-plan.md index e4810e5efea4..dd16ca7cee7c 100644 --- a/.github/copilot-issue-verification-action-plan.md +++ b/.github/copilot-issue-verification-action-plan.md @@ -4,7 +4,7 @@ ms.author: wpickett ms.date: 11-13-2025 --- -# GitHub Issue Analysis and Action Plan Prompt for ASP.NET Core Documentation +# GitHub issue analysis and action plan prompt for ASP.NET Core documentation ## Goal Analyze the GitHub issue and provide a **structured report** determining: @@ -20,38 +20,38 @@ The report should be suitable for posting directly in the issue discussion. ### 1. Information Gathering Collect and review: -- The **issue title, description, and all comments** -- The **published documentation** (via the provided URL) -- The **source file(s)** in the repository -- Any **linked issues, PRs, or external references** -- **Environment details**: .NET version, tooling versions (VS, VS Code, CLI, EF Core, etc.) -- **Code samples or error messages** mentioned in the issue +* The **issue title, description, and all comments** +* The **published documentation** (via the provided URL) +* The **source file(s)** in the repository +* Any **linked issues, PRs, or external references** +* **Environment details**: .NET version, tooling versions (VS, VS Code, CLI, EF Core, etc.) +* **Code samples or error messages** mentioned in the issue ### 1.5 Source File Analysis When examining source files: -- **Provide direct GitHub permalinks** to specific lines or sections -- **Note exact line numbers** for proposed changes -- **Include line number ranges** in GitHub URLs using `#L-L` format -- **Quote current content** from specific lines before proposing changes -- **Use permalinks with commit SHA** when referencing specific versions +* **Provide direct GitHub permalinks** to specific lines or sections +* **Note exact line numbers** for proposed changes +* **Include line number ranges** in GitHub URLs using `#L-L` format +* **Quote current content** from specific lines before proposing changes +* **Use permalinks with commit SHA** when referencing specific versions Example format for file references: -- Single line: `https://github.com/owner/repo/blob/main/file.md#L123` -- Line range: `https://github.com/owner/repo/blob/main/file.md#L123-L145` -- Permalink: `https://github.com/owner/repo/blob//file.md#L123` +* Single line: `https://github.com/owner/repo/blob/main/file.md#L123` +* Line range: `https://github.com/owner/repo/blob/main/file.md#L123-L145` +* Permalink: `https://github.com/owner/repo/blob//file.md#L123` ### 2. Validation Criteria Determine if the issue is: -- **In scope**: Related to ASP.NET Core documentation (not product bugs) -- **Accurate**: The reported problem genuinely exists -- **Clear**: Sufficient information to take action -- **Current**: Applies to supported .NET versions +* **In scope**: Related to ASP.NET Core documentation (not product bugs) +* **Accurate**: The reported problem genuinely exists +* **Clear**: Sufficient information to take action +* **Current**: Applies to supported .NET versions ### 3. Translation Requirements If any content is not in English: -- Include the original text in a quote block -- Provide complete English translation -- Label clearly as "Original" and "Translation" +* Include the original text in a quote block +* Provide complete English translation +* Label clearly as "Original" and "Translation" --- @@ -123,25 +123,25 @@ If any content is not in English: ## 🎯 Action Plan 1. **Edit file:** [`aspnetcore/path/to/file.md`](https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/path/to/file.md) - - Navigate to: [Line 123](https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/path/to/file.md#L123) - - Find section: "Exact Section Heading" - - After text: "last sentence before insertion point" - - Insert: [!NOTE] block with explanation + * Navigate to: [Line 123](https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/path/to/file.md#L123) + * Find section: "Exact Section Heading" + * After text: "last sentence before insertion point" + * Insert: [!NOTE] block with explanation 2. **Update sample:** [`path/to/sample.cs`](https://github.com/dotnet/AspNetCore.Docs/blob/main/path/to/sample.cs) - - Navigate to: [Lines 45-67](https://github.com/dotnet/AspNetCore.Docs/blob/main/path/to/sample.cs#L45-L67) - - Modify method: `MethodName()` - - Change: Update to use new pattern + * Navigate to: [Lines 45-67](https://github.com/dotnet/AspNetCore.Docs/blob/main/path/to/sample.cs#L45-L67) + * Modify method: `MethodName()` + * Change: Update to use new pattern ## ⚠️ Considerations -- Verify change applies to .NET [version] -- Check if similar updates needed in related articles -- Consider adding cross-references to [related topic] +* Verify change applies to .NET [version] +* Check if similar updates needed in related articles +* Consider adding cross-references to [related topic] ## 🔗 References -- Published article: [URL] -- Related issue: #[number] -- Microsoft Learn docs: [relevant MS docs link] +* Published article: [URL] +* Related issue: #[number] +* Microsoft Learn docs: [relevant MS docs link] ``` #### For Invalid Issues @@ -157,14 +157,14 @@ If any content is not in English: ## 💡 Recommendation -- [Close with explanation] -- [Redirect to appropriate repository] -- [Request additional information] -- [Convert to discussion] +* [Close with explanation] +* [Redirect to appropriate repository] +* [Request additional information] +* [Convert to discussion] ## 🔗 Alternative Resources -- [Link to relevant documentation] -- [Link to appropriate repository for product issues] +* [Link to relevant documentation] +* [Link to appropriate repository for product issues] ``` --- @@ -172,41 +172,41 @@ If any content is not in English: ## Special Instructions ### Line Number Guidelines -- **Always inspect the actual source file** to determine accurate line numbers -- **Provide line ranges** rather than single lines when changes affect multiple lines -- **Use GitHub's line highlighting** format in URLs (#L123 for single, #L123-L145 for range) -- **Quote the existing content** at those lines to confirm accuracy -- **Consider context lines** - include a few lines before/after for clarity -- **Update line numbers** if the file has changed since issue creation +* **Always inspect the actual source file** to determine accurate line numbers +* **Provide line ranges** rather than single lines when changes affect multiple lines +* **Use GitHub's line highlighting** format in URLs (#L123 for single, #L123-L145 for range) +* **Quote the existing content** at those lines to confirm accuracy +* **Consider context lines** - include a few lines before/after for clarity +* **Update line numbers** if the file has changed since issue creation ### Content Block Usage Only recommend using special blocks when truly appropriate, they should not be overused: -- `[!IMPORTANT]`: Security issues, breaking changes, data loss risks -- `[!WARNING]`: Common mistakes, deprecation notices -- `[!NOTE]`: Helpful clarifications, version-specific info -- `[!TIP]`: Best practices, productivity hints +* `[!IMPORTANT]`: Security issues, breaking changes, data loss risks +* `[!WARNING]`: Common mistakes, deprecation notices +* `[!NOTE]`: Helpful clarifications, version-specific info +* `[!TIP]`: Best practices, productivity hints ### Code Samples -- Use appropriate language identifier for syntax highlighting -- Include necessary `using` statements or imports -- Add comments for complex logic -- Ensure samples are complete and runnable +* Use appropriate language identifier for syntax highlighting +* Include necessary `using` statements or imports +* Add comments for complex logic +* Ensure samples are complete and runnable ### Scope Boundaries **DO:** -- Focus on documentation clarity and accuracy -- Address missing information -- Fix technical inaccuracies -- Improve code samples +* Focus on documentation clarity and accuracy +* Address missing information +* Fix technical inaccuracies +* Improve code samples **DON'T:** -- Attempt to fix product bugs through documentation -- Make architectural recommendations -- Add opinions or preferences -- Modify unrelated sections +* Attempt to fix product bugs through documentation +* Make architectural recommendations +* Add opinions or preferences +* Modify unrelated sections ## Issue labels -- Upon completion of the report, set the `ai-reviewed-issue-reported-action-plan` label for the issue. +* Upon completion of the report, set the `ai-reviewed-issue-reported-action-plan` label for the issue. ### Common Issue Types 1. **Missing information**: Add clarifying content From 3d1a99eb4acf31d7c4a4f1855c6f6bfcf184e9a7 Mon Sep 17 00:00:00 2001 From: wadepickett Date: Thu, 13 Nov 2025 15:08:38 -0800 Subject: [PATCH 4/8] Removed quick decision tree --- .../copilot-issue-verification-action-plan.md | 99 ++++++++----------- 1 file changed, 43 insertions(+), 56 deletions(-) diff --git a/.github/copilot-issue-verification-action-plan.md b/.github/copilot-issue-verification-action-plan.md index dd16ca7cee7c..d8da6d8a6998 100644 --- a/.github/copilot-issue-verification-action-plan.md +++ b/.github/copilot-issue-verification-action-plan.md @@ -8,9 +8,10 @@ ms.date: 11-13-2025 ## Goal Analyze the GitHub issue and provide a **structured report** determining: -1. Whether the issue is valid and actionable -2. The exact documentation changes required (if applicable) -3. A clear action plan that can guide PR creation +1. Whether the issue is valid and actionable. +1. Whether the issue is whithin scope of the articles the issue relates to, or if a new article is needed. +1. The exact documentation changes required (if applicable). +1. A clear action plan that can guide PR creation. The report should be suitable for posting directly in the issue discussion. @@ -20,38 +21,38 @@ The report should be suitable for posting directly in the issue discussion. ### 1. Information Gathering Collect and review: -* The **issue title, description, and all comments** -* The **published documentation** (via the provided URL) -* The **source file(s)** in the repository -* Any **linked issues, PRs, or external references** -* **Environment details**: .NET version, tooling versions (VS, VS Code, CLI, EF Core, etc.) -* **Code samples or error messages** mentioned in the issue +* The **issue title, description, and all comments**. +* The **published documentation** (via the provided URL). +* The **source file(s)** in the repository. +* Any **linked issues, PRs, or external references**. +* **Environment details**: .NET version, tooling versions (VS, VS Code, CLI, EF Core, etc.). +* **Code samples or error messages** mentioned in the issue. ### 1.5 Source File Analysis When examining source files: -* **Provide direct GitHub permalinks** to specific lines or sections -* **Note exact line numbers** for proposed changes -* **Include line number ranges** in GitHub URLs using `#L-L` format -* **Quote current content** from specific lines before proposing changes -* **Use permalinks with commit SHA** when referencing specific versions +* **Provide direct GitHub permalinks** to specific lines or sections. +* **Note exact line numbers** for proposed changes. +* **Include line number ranges** in GitHub URLs using `#L-L` format. +* **Quote current content** from specific lines before proposing changes. +* **Use permalinks with commit SHA** when referencing specific versions. Example format for file references: -* Single line: `https://github.com/owner/repo/blob/main/file.md#L123` -* Line range: `https://github.com/owner/repo/blob/main/file.md#L123-L145` -* Permalink: `https://github.com/owner/repo/blob//file.md#L123` +* Single line: `https://github.com/owner/repo/blob/main/file.md#L123`. +* Line range: `https://github.com/owner/repo/blob/main/file.md#L123-L145`. +* Permalink: `https://github.com/owner/repo/blob//file.md#L123`. ### 2. Validation Criteria Determine if the issue is: -* **In scope**: Related to ASP.NET Core documentation (not product bugs) -* **Accurate**: The reported problem genuinely exists -* **Clear**: Sufficient information to take action -* **Current**: Applies to supported .NET versions +* **In scope**: Related to ASP.NET Core documentation (not product bugs). +* **Accurate**: The reported problem genuinely exists. +* **Clear**: Sufficient information to take action. +* **Current**: Applies to supported .NET versions. ### 3. Translation Requirements If any content is not in English: -* Include the original text in a quote block -* Provide complete English translation -* Label clearly as "Original" and "Translation" +* Include the original text in a quote block. +* Provide complete English translation. +* Label clearly as "Original" and "Translation". --- @@ -172,12 +173,12 @@ If any content is not in English: ## Special Instructions ### Line Number Guidelines -* **Always inspect the actual source file** to determine accurate line numbers -* **Provide line ranges** rather than single lines when changes affect multiple lines -* **Use GitHub's line highlighting** format in URLs (#L123 for single, #L123-L145 for range) -* **Quote the existing content** at those lines to confirm accuracy -* **Consider context lines** - include a few lines before/after for clarity -* **Update line numbers** if the file has changed since issue creation +* **Always inspect the actual source file** to determine accurate line numbers. +* **Provide line ranges** rather than single lines when changes affect multiple lines. +* **Use GitHub's line highlighting** format in URLs (#L123 for single, #L123-L145 for range). +* **Quote the existing content** at those lines to confirm accuracy. +* **Consider context lines** - include a few lines before/after for clarity. +* **Update line numbers** if the file has changed since issue creation. ### Content Block Usage Only recommend using special blocks when truly appropriate, they should not be overused: @@ -187,23 +188,23 @@ Only recommend using special blocks when truly appropriate, they should not be o * `[!TIP]`: Best practices, productivity hints ### Code Samples -* Use appropriate language identifier for syntax highlighting -* Include necessary `using` statements or imports -* Add comments for complex logic -* Ensure samples are complete and runnable +* Use appropriate language identifier for syntax highlighting. +* Include necessary `using` statements or imports. +* Add comments for complex logic. +* Ensure samples are complete and runnable. ### Scope Boundaries **DO:** -* Focus on documentation clarity and accuracy -* Address missing information -* Fix technical inaccuracies -* Improve code samples +* Focus on documentation clarity and accuracy. +* Address missing information. +* Fix technical inaccuracies. +* Improve code samples. **DON'T:** -* Attempt to fix product bugs through documentation -* Make architectural recommendations -* Add opinions or preferences -* Modify unrelated sections +* Attempt to fix product bugs through documentation. +* Make architectural recommendations. +* Add opinions or preferences. +* Modify unrelated sections. ## Issue labels * Upon completion of the report, set the `ai-reviewed-issue-reported-action-plan` label for the issue. @@ -216,17 +217,3 @@ Only recommend using special blocks when truly appropriate, they should not be o 5. **Missing prerequisites**: Add setup steps --- - -## Quick Decision Tree - -``` -Is this a documentation issue? -├── NO → Redirect to product repo -└── YES → Is the information accurate? - ├── NO → Provide correction - └── YES → Is it clear enough? - ├── NO → Clarify/expand - └── YES → Is it complete? - ├── NO → Add missing info - └── YES → Consider if enhancement improves value -``` \ No newline at end of file From c21a116cd4f3888a12a1f20f840cb8a6decce665 Mon Sep 17 00:00:00 2001 From: Wade Pickett Date: Thu, 13 Nov 2025 20:55:13 -0800 Subject: [PATCH 5/8] Update .github/copilot-issue-verification-action-plan.md Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --- .github/copilot-issue-verification-action-plan.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/copilot-issue-verification-action-plan.md b/.github/copilot-issue-verification-action-plan.md index d8da6d8a6998..b823c0f39b22 100644 --- a/.github/copilot-issue-verification-action-plan.md +++ b/.github/copilot-issue-verification-action-plan.md @@ -9,7 +9,7 @@ ms.date: 11-13-2025 ## Goal Analyze the GitHub issue and provide a **structured report** determining: 1. Whether the issue is valid and actionable. -1. Whether the issue is whithin scope of the articles the issue relates to, or if a new article is needed. +1. Whether the issue is within scope of the articles the issue relates to, or if a new article is needed. 1. The exact documentation changes required (if applicable). 1. A clear action plan that can guide PR creation. From 330a5a87884043da1760acd37c66c345c7913758 Mon Sep 17 00:00:00 2001 From: Wade Pickett Date: Thu, 13 Nov 2025 20:57:36 -0800 Subject: [PATCH 6/8] Apply suggestions from code review --- .github/copilot-issue-verification-action-plan.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/copilot-issue-verification-action-plan.md b/.github/copilot-issue-verification-action-plan.md index b823c0f39b22..9d8455aadbb4 100644 --- a/.github/copilot-issue-verification-action-plan.md +++ b/.github/copilot-issue-verification-action-plan.md @@ -1,7 +1,7 @@ --- author: tdykstra ms.author: wpickett -ms.date: 11-13-2025 +ms.date: 11/13/2025 --- # GitHub issue analysis and action plan prompt for ASP.NET Core documentation From ad63603e91e7c9813a25275fa8466816dc2b2af1 Mon Sep 17 00:00:00 2001 From: Wade Pickett Date: Thu, 13 Nov 2025 20:59:59 -0800 Subject: [PATCH 7/8] Apply suggestions from code review --- .github/copilot-issue-verification-action-plan.md | 1 + 1 file changed, 1 insertion(+) diff --git a/.github/copilot-issue-verification-action-plan.md b/.github/copilot-issue-verification-action-plan.md index 9d8455aadbb4..54f08f7ec9b6 100644 --- a/.github/copilot-issue-verification-action-plan.md +++ b/.github/copilot-issue-verification-action-plan.md @@ -1,4 +1,5 @@ --- +ai-usage: ai-assisted author: tdykstra ms.author: wpickett ms.date: 11/13/2025 From 5281fa7e0cf6bd5b00d3c7c195edb22d8cb58a87 Mon Sep 17 00:00:00 2001 From: Wade Pickett Date: Thu, 13 Nov 2025 21:01:22 -0800 Subject: [PATCH 8/8] Fix numbering in issue verification action plan Updated the numbering of the goals in the action plan for clarity. --- .github/copilot-issue-verification-action-plan.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/.github/copilot-issue-verification-action-plan.md b/.github/copilot-issue-verification-action-plan.md index 54f08f7ec9b6..d74c96c416f4 100644 --- a/.github/copilot-issue-verification-action-plan.md +++ b/.github/copilot-issue-verification-action-plan.md @@ -10,9 +10,9 @@ ms.date: 11/13/2025 ## Goal Analyze the GitHub issue and provide a **structured report** determining: 1. Whether the issue is valid and actionable. -1. Whether the issue is within scope of the articles the issue relates to, or if a new article is needed. -1. The exact documentation changes required (if applicable). -1. A clear action plan that can guide PR creation. +2. Whether the issue is within scope of the articles the issue relates to, or if a new article is needed. +3. The exact documentation changes required (if applicable). +4. A clear action plan that can guide PR creation. The report should be suitable for posting directly in the issue discussion.