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 e1c7c7a50e
Add 18 new prompts files (#56) 
* Add prompts for .NET best practices, design pattern review, and GitHub Copilot suggestions

- Introduced a comprehensive prompt for ensuring .NET/C# code adheres to best practices, covering documentation, design patterns, dependency injection, resource management, async patterns, testing standards, configuration, AI integration, error handling, performance, security, and code quality.
- Added a prompt for reviewing C#/.NET code for design pattern implementation, providing a checklist for required patterns, architecture, best practices, SOLID principles, performance, maintainability, testability, security, documentation, code clarity, and clean code.
- Created prompts for suggesting relevant GitHub Copilot chatmodes and prompts based on the current repository context, including a structured process for fetching available chatmodes/prompts, scanning local files, and presenting options with rationale.
- Developed a prompt for updating Azure Verified Modules (AVM) in Bicep files, detailing the process for scanning, checking for updates, validating, and handling breaking changes.
- Implemented a prompt for updating implementation plans with new requirements, ensuring machine-readable output and adherence to a strict template.
- Added a prompt for updating the llms.txt file to reflect changes in documentation or specifications, focusing on compliance with the llmstxt specification.
- Created a prompt for updating markdown file indices with files from specified folders, including options for table structures and update strategies.
- Developed a prompt for updating object-oriented component documentation, following industry best practices and ensuring alignment with current implementations.
- Added a prompt for updating specification files, emphasizing clarity, structure, and compliance with established documentation standards.

* CHANGE: Update implementation plan prompt formatting

- Renamed prompt title for clarity.
- Added spacing for improved readability.
- Enhanced structure to ensure compliance with template validation rules.

* CHANGE: Fix typo in .NET best practices prompt

- Corrected "soltion" to "solution" in the prompt description.
2025-07-07 16:17:09 +10:00

961 B
Raw Permalink 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)