Daniel Scott-Raynsford e1c7c7a50e

* 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

1.3 KiB

Raw Blame History

mode

description

tools

agent

Create GitHub Issues for unimplemented requirements from specification files using feature_request.yml template.

codebase

github

create_issue

search_issues

update_issue

Create GitHub Issues for Unmet Specification Requirements

Create GitHub Issues for unimplemented requirements in the specification at ${file}.

Process

Analyze specification file to extract all requirements
Check codebase implementation status for each requirement
Search existing issues using search_issues to avoid duplicates
Create new issue per unimplemented requirement using create_issue
Use feature_request.yml template (fallback to default)

Requirements

One issue per unimplemented requirement from specification
Clear requirement ID and description mapping
Include implementation guidance and acceptance criteria
Verify against existing issues before creation

Issue Content

Title: Requirement ID and brief description
Description: Detailed requirement, implementation method, and context
Labels: feature, enhancement (as appropriate)

Implementation Check

Search codebase for related code patterns
Check related specification files in /spec/ directory
Verify requirement isn't partially implemented

1.3 KiB Raw Blame History