Prompt file imported from diginsight/knowledgehub (.github/prompts/10.00-application-development/issue-generate-analysis-from-current-conversation.prompt.md). Copyright stays with the author.

Generate analysis from current conversation

Name: issue-generate-analysis
Author: diginsight

Goal

Generate a comprehensive issue markdown document using the enhanced structure defined in the file ISSUE Template.md. The issue markdown document should be created in the folder /src/docs/90. Issues and named as YYYYMMDD - [Issue Title].md.

Instructions

1. Analyze Current Conversation

Analyze the current conversation and identify the following information:

IssueTitle: A concise, descriptive title about the issue identified in the current conversation
DatePrefix: The current date in the format YYYYMMDD (e.g., 20251107)
Author: The current user name (e.g., "Dario Airoldi")
Severity: Assess the severity level (Low/Medium/High/Critical)
Component: Identify the affected component or project
Framework: Determine the target framework version

2. Read and Understand Template Structure

Read the template file located at: .github/copilot/templates/ISSUE Template.md

Understand the enhanced structure including:

Header with metadata (Date, Author, Status, Severity, Component, Framework)
Table of Contents with emoji navigation
Comprehensive sections with detailed subsections
Modern formatting with tables, code blocks, and checklists

3. Create New Issue Document

Create a new issue document in the folder: /src/docs/90. Issues

Name the document as: <DatePrefix> - <IssueTitle>.md

4. Fill Content from Conversation Analysis

Analyze the current debugging conversation and fill ALL sections of the issue report:

Required Sections to Complete:

📝 DESCRIPTION: Brief description, error messages, and impact points
🔍 CONTEXT INFORMATION: Environment details, exception details, call stack, variable values
🔬 ANALYSIS: Root cause analysis, impact assessment, affected workflows
🔄 REPRODUCTION STEPS: Step-by-step reproduction and affected code locations
✅ SOLUTION IMPLEMENTED: Fix overview, code changes, solution features (if solution was discussed)
📚 ADDITIONAL INFORMATION: Testing recommendations, migration considerations, performance impact
✔️ RESOLUTION STATUS: Current status, verification checklist, follow-up actions
🎓 LESSONS LEARNED: What went wrong/right, improvements for future
📎 APPENDIX: Additional reference materials and examples

Content Guidelines:

Use emojis in section headers for visual appeal
Include comprehensive tables for structured data
Add code snippets with proper syntax highlighting
Use checkboxes for actionable items
Include links and references where applicable
Maintain professional technical writing style

5. Quality Assurance

Ensure the generated document:

✅ Follows the exact template structure
✅ Includes Table of Contents with proper anchor links
✅ Contains all emoji headers as specified
✅ Has comprehensive content in each section
✅ Uses consistent formatting throughout
✅ Includes actionable follow-up items
✅ Provides clear reproduction steps
✅ Documents lessons learned for future prevention

# Generate analysis from current conversation ## Goal Generate a comprehensive issue markdown document using the enhanced structure defined in the file `ISSUE Template.md`. The issue markdown document should be created in the folder `/src/docs/90. Issues` and named as `YYYYMMDD - [Issue Title].md`. ## Instructions ### 1. Analyze Current Conversation Analyze the current conversation and identify the following information: - **IssueTitle**: A concise, descriptive title about the issue identified in the current conversation - **DatePrefix**: The current date in the format `YYYYMMDD` (e.g., `20251107`) - **Author**: The current user name (e.g., "Dario Airoldi") - **Severity**: Assess the severity level (Low/Medium/High/Critical) - **Component**: Identify the affected component or project - **Framework**: Determine the target framework version ### 2. Read and Understand Template Structure Read the template file located at: `.github/copilot/templates/ISSUE Template.md` Understand the enhanced structure including: - **Header with metadata** (Date, Author, Status, Severity, Component, Framework) - **Table of Contents** with emoji navigation - **Comprehensive sections** with detailed subsections - **Modern formatting** with tables, code blocks, and checklists ### 3. Create New Issue Document Create a new issue document in the folder: `/src/docs/90. Issues` Name the document as: `<DatePrefix> - <IssueTitle>.md` ### 4. Fill Content from Conversation Analysis Analyze the current debugging conversation and fill ALL sections of the issue report: #### Required Sections to Complete: - **📝 DESCRIPTION**: Brief description, error messages, and impact points - **🔍 CONTEXT INFORMATION**: Environment details, exception details, call stack, variable values - **🔬 ANALYSIS**: Root cause analysis, impact assessment, affected workflows - **🔄 REPRODUCTION STEPS**: Step-by-step reproduction and affected code locations - **✅ SOLUTION IMPLEMENTED**: Fix overview, code changes, solution features (if solution was discussed) - **📚 ADDITIONAL INFORMATION**: Testing recommendations, migration considerations, performance impact - **✔️ RESOLUTION STATUS**: Current status, verification checklist, follow-up actions - **🎓 LESSONS LEARNED**: What went wrong/right, improvements for future - **📎 APPENDIX**: Additional reference materials and examples #### Content Guidelines: - Use **emojis** in section headers for visual appeal - Include **comprehensive tables** for structured data - Add **code snippets** with proper syntax highlighting - Use **checkboxes** for actionable items - Include **links and references** where applicable - Maintain **professional technical writing** style ### 5. Quality Assurance Ensure the generated document: - ✅ Follows the exact template structure - ✅ Includes Table of Contents with proper anchor links - ✅ Contains all emoji headers as specified - ✅ Has comprehensive content in each section - ✅ Uses consistent formatting throughout - ✅ Includes actionable follow-up items - ✅ Provides clear reproduction steps - ✅ Documents lessons learned for future prevention

{ "prompt": "# Generate analysis from current conversation\n\n## Goal\nGenerate a comprehensive issue markdown document using the enhanced structure defined in the file `ISSUE Template.md`.\nThe issue markdown document should be created in the folder `/src/docs/90. Issues` and named as `YYYYMMDD - [Issue Title].md`.\n\n## Instructions\n\n### 1. Analyze Current Conversation\nAnalyze the current conversation and identify the following information:\n- **IssueTitle**: A concise, descriptive title about the issue identified in the current conversation\n- **DatePrefix**: The current date in the format `YYYYMMDD` (e.g., `20251107`)\n- **Author**: The current user name (e.g., \"Dario Airoldi\")\n- **Severity**: Assess the severity level (Low/Medium/High/Critical)\n- **Component**: Identify the affected component or project\n- **Framework**: Determine the target framework version\n\n### 2. Read and Understand Template Structure\nRead the template file located at:\n`.github/copilot/templates/ISSUE Template.md`\n\nUnderstand the enhanced structure including:\n- **Header with metadata** (Date, Author, Status, Severity, Component, Framework)\n- **Table of Contents** with emoji navigation\n- **Comprehensive sections** with detailed subsections\n- **Modern formatting** with tables, code blocks, and checklists\n\n### 3. Create New Issue Document\nCreate a new issue document in the folder:\n`/src/docs/90. Issues`\n\nName the document as:\n`<DatePrefix> - <IssueTitle>.md`\n\n### 4. Fill Content from Conversation Analysis\nAnalyze the current debugging conversation and fill ALL sections of the issue report:\n\n#### Required Sections to Complete:\n- **📝 DESCRIPTION**: Brief description, error messages, and impact points\n- **🔍 CONTEXT INFORMATION**: Environment details, exception details, call stack, variable values\n- **🔬 ANALYSIS**: Root cause analysis, impact assessment, affected workflows\n- **🔄 REPRODUCTION STEPS**: Step-by-step reproduction and affected code locations\n- **✅ SOLUTION IMPLEMENTED**: Fix overview, code changes, solution features (if solution was discussed)\n- **📚 ADDITIONAL INFORMATION**: Testing recommendations, migration considerations, performance impact\n- **✔️ RESOLUTION STATUS**: Current status, verification checklist, follow-up actions\n- **🎓 LESSONS LEARNED**: What went wrong/right, improvements for future\n- **📎 APPENDIX**: Additional reference materials and examples\n\n#### Content Guidelines:\n- Use **emojis** in section headers for visual appeal\n- Include **comprehensive tables** for structured data\n- Add **code snippets** with proper syntax highlighting\n- Use **checkboxes** for actionable items\n- Include **links and references** where applicable\n- Maintain **professional technical writing** style\n\n### 5. Quality Assurance\nEnsure the generated document:\n- ✅ Follows the exact template structure\n- ✅ Includes Table of Contents with proper anchor links\n- ✅ Contains all emoji headers as specified\n- ✅ Has comprehensive content in each section\n- ✅ Uses consistent formatting throughout\n- ✅ Includes actionable follow-up items\n- ✅ Provides clear reproduction steps\n- ✅ Documents lessons learned for future prevention", "variables": [], "notes": "Generate analysis from current conversation Tools: codebase, fetch. Arguments: topic=\"Your Article Topic\" outline=\"key points to cover\".", "metadata": { "source": { "provider": "github-prompts", "repository": "https://github.com/diginsight/knowledgehub", "path": ".github/prompts/10.00-application-development/issue-generate-analysis-from-current-conversation.prompt.md", "ref": "91d985f743b44c2067f1fc59535e8c32657b2120", "url": "https://github.com/diginsight/knowledgehub/blob/91d985f743b44c2067f1fc59535e8c32657b2120/.github/prompts/10.00-application-development/issue-generate-analysis-from-current-conversation.prompt.md", "key": "diginsight/knowledgehub/.github/prompts/10.00-application-development/issue-generate-analysis-from-current-conversation.prompt.md" } }, "model_hints": [ "claude-sonnet-4.5" ] }

issue-generate-analysis

About