This change adds a skill that can analyze the resources within an Azure
resource group, determine the relationships between them, and then
generate a Markdown file containing the relevant details. The Markdown
file includes a Mermaid diagram showing the relationships.
Updated the instructionsUsage template in constants.mjs to clarify that task-specific instruction files should be created in the .github/instructions/ folder with the pattern *.instructions.md (e.g., .github/instructions/my-csharp-rules.instructions.md), instead of the confusing original wording that mentioned both .github/.instructions.md files and .github/instructions folder.
Co-authored-by: aaronpowell <434140+aaronpowell@users.noreply.github.com>
* Initial plan
* Add DevOps resources: agents, instructions, and prompt
* Replace redundant GitHub Actions instructions with expert agent
* Make DevOps resources more generic for easier maintenance
* Remove optional model field to align with repository conventions
* Reduce code examples to focus on principles and guidance
* Add DevOps Expert agent following infinity loop principle
---------
Co-authored-by: Copilot <198982749+Copilot@users.noreply.github.com>
Co-authored-by: benjisho-aidome <218995725+benjisho-aidome@users.noreply.github.com>
Co-authored-by: Matt Soucoup <masoucou@microsoft.com>
This skill outlines the management of NuGet packages in .NET projects, emphasizing the use of the `dotnet` CLI for package operations and detailing workflows for adding, removing, and updating package versions.
- Replace static github-mcp-registry.json with live API calls
- Fetch from https://api.mcp.github.com/v0.1/servers/ with pagination support
- Extract displayName from GitHub metadata for better matching
- Implement smart matching logic:
* Case-insensitive comparison
* Match against both displayName and full name
* Strip common suffixes like -mcp-server for pattern matching
- Make build process async to support API calls
- Cache registry data to only hit API once per build run
- Remove obsolete github-mcp-registry.json file
Benefits:
- No more manual updates to registry data
- Always uses latest MCP registry information
- Improved server name matching resilience
- Successfully loads all 54 servers from registry
