Daniel Scott-Raynsford 8229a03986 feat: Add comprehensive documentation prompts for OO components, specifications, and .NET best practices

- 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.

2025-07-06 11:01:46 +12:00

1.6 KiB

Raw Blame History

mode

description

tools

agent

Update Azure Verified Modules to latest versions in Bicep files.

changes

codebase

editFiles

fetch

runCommands

azure_get_deployment_best_practices

azure_get_schema_for_Bicep

Update Azure Verified Modules in Bicep Files

Update Bicep file ${file} to use latest Azure Verified Module (AVM) versions.

Process

Scan: Extract AVM modules and current versions from ${file}
Check: Fetch latest versions from MCR: https://mcr.microsoft.com/v2/bicep/avm/res/{service}/{resource}/tags/list
Compare: Parse semantic versions to identify updates
Review: For breaking changes, fetch docs from: https://github.com/Azure/bicep-registry-modules/tree/main/avm/res/{service}/{resource}
Update: Apply version updates and parameter changes
Validate: Run bicep lint to ensure compliance

Breaking Change Policy

⚠️ PAUSE for approval if updates involve:

Incompatible parameter changes
Security/compliance modifications
Behavioral changes

Output Format

Display results in table with icons:

Module	Current	Latest	Status	Action	Docs
avm/res/compute/vm	0.1.0	0.2.0	🔄	Updated	📖
avm/res/storage/account	0.3.0	0.3.0	✅	Current	📖

Icons

🔄 Updated
✅ Current
⚠️ Manual review required
❌ Failed
📖 Documentation

Requirements

Use MCR tags API only for version discovery
Parse JSON tags array and sort by semantic versioning
Maintain Bicep file validity and linting compliance

1.6 KiB Raw Blame History