8229a03986
- Introduced a prompt for creating standardized documentation for object-oriented components, adhering to industry best practices and architectural standards. - Added a prompt for generating new specification files optimized for Generative AI consumption, including best practices for AI-ready specifications. - Created a prompt for reviewing .NET/C# code against best practices, focusing on documentation, design patterns, dependency injection, and error handling. - Developed a prompt for reviewing design pattern implementations in .NET/C# code, providing a checklist and improvement focus areas. - Implemented a prompt for updating Azure Verified Modules in Bicep files to the latest versions, including a breaking change policy. - Added a prompt for updating existing implementation plans with new requirements or updates to existing code. - Created a prompt for updating the llms.txt file to reflect changes in documentation or specifications. - Developed a prompt for updating markdown file sections with an index/table of files from specified folders. - Introduced a prompt for updating existing object-oriented component documentation based on current implementation. - Added a prompt for updating existing specifications based on new requirements or code updates.
29 lines
968 B
Markdown
29 lines
968 B
Markdown
---
|
|
mode: 'agent'
|
|
description: 'Create GitHub Issue for feature request from specification file using feature_request.yml template.'
|
|
tools: ['codebase', 'search', 'github', 'create_issue', 'search_issues', 'update_issue']
|
|
---
|
|
# Create GitHub Issue from Specification
|
|
|
|
Create GitHub Issue for the specification at `${file}`.
|
|
|
|
**Process:**
|
|
|
|
1. Analyze specification file to extract requirements
|
|
2. Check existing issues using `search_issues`
|
|
3. Create new issue using `create_issue` or update existing with `update_issue`
|
|
4. Use `feature_request.yml` template (fallback to default)
|
|
|
|
**Requirements:**
|
|
|
|
- Single issue for the complete specification
|
|
- Clear title identifying the specification
|
|
- Include only changes required by the specification
|
|
- Verify against existing issues before creation
|
|
|
|
**Issue Content:**
|
|
|
|
- Title: Feature name from specification
|
|
- Description: Problem statement, proposed solution, and context
|
|
- Labels: feature, enhancement (as appropriate)
|