d260c65769
- Created a prompt for .NET/C# best practices to ensure code quality and adherence to standards. - Added a design pattern review prompt for evaluating C#/.NET code implementations. - Introduced prompts for suggesting relevant GitHub Copilot chatmodes and prompts based on repository context. - Developed a prompt for updating Azure Verified Modules in Bicep files to the latest versions. - Implemented a prompt for updating implementation plans with new requirements and features. - Created a prompt for updating the llms.txt file to reflect changes in documentation or specifications. - Added a prompt for updating markdown file indexes with files from specified folders. - Developed a prompt for updating object-oriented component documentation according to best practices. - Created a prompt for updating specification files to align with new requirements and ensure AI-readiness.
29 lines
985 B
Markdown
29 lines
985 B
Markdown
---
|
|
mode: 'agent'
|
|
description: Create GitHub Issues from implementation plan phases using feature_request.yml or chore_request.yml templates.
|
|
tools: ['codebase', 'search', 'github', 'create_issue', 'search_issues', 'update_issue']
|
|
---
|
|
# Create GitHub Issue from Implementation Plan
|
|
|
|
Create GitHub Issues for the implementation plan at `${file}`.
|
|
|
|
## Process
|
|
|
|
1. Analyze plan file to identify phases
|
|
2. Check existing issues using `search_issues`
|
|
3. Create new issue per phase using `create_issue` or update existing with `update_issue`
|
|
4. Use `feature_request.yml` or `chore_request.yml` templates (fallback to default)
|
|
|
|
## Requirements
|
|
|
|
- One issue per implementation phase
|
|
- Clear, structured titles and descriptions
|
|
- Include only changes required by the plan
|
|
- Verify against existing issues before creation
|
|
|
|
## Issue Content
|
|
|
|
- Title: Phase name from implementation plan
|
|
- Description: Phase details, requirements, and context
|
|
- Labels: Appropriate for issue type (feature/chore)
|