josiadmin/awesome-copilot
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
awesome-copilot/prompts/create-github-issue-feature-from-specification.prompt.md
Daniel Scott-Raynsford d260c65769 Add prompts for .NET best practices, design pattern review, GitHub Copilot suggestions, and various update tasks 
- 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.
2025-07-07 12:51:24 +12:00

959 B
Raw Blame History

mode description tools
agent Create GitHub Issue for feature request from specification file using feature_request.yml template.
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)