file-test-bug

Creates a GitHub issue in microsoft/github-copilot-for-azure for integration test failures.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "file-test-bug" with this command: npx skills add microsoft/github-copilot-for-azure/microsoft-github-copilot-for-azure-file-test-bug

File Test Bug

Creates a GitHub issue in microsoft/github-copilot-for-azure for integration test failures.

Input

  • Skill name (required): e.g., azure-rbac , appinsights-instrumentation

  • Test run (optional): Timestamp of test run. Defaults to most recent with logs for the skill.

Steps

  • Ask user for skill name if not provided

  • Parse tests/reports/junit.xml for failures matching the skill

  • Find test run directory (specified or most recent with matching logs)

  • Read agent-metadata.md from tests/reports/test-run-<timestamp>/<skillname>-<testname>/

  • For each failure, read the actual line of code from the test file using the location (file:line) from junit.xml

  • REQUIRED - Write diagnosis BEFORE creating issue:

  • Analyze the agent-metadata.md to understand what the agent did

  • Compare agent behavior to what the test expected (from the assertion)

  • Identify the root cause (skill issue, test issue, or model behavior)

  • Write 2-3 sentences per failed test explaining WHY it failed

  • Suggest potential fixes (update skill, update test, or update fixtures)

  • Create issue via github-mcp-server-create_issue :

owner: microsoft repo: github-copilot-for-azure title: Integration test failure in <skill-name> labels: ["bug", "integration-test"] body: |

Failed Tests

  • <test-name>: <error message>

Diagnosis

Root Cause

<1-2 sentences explaining WHY the test failed based on agent-metadata.md analysis>

Analysis per Test

  • <test-name>: <what agent did vs what test expected>

Suggested Fix

<one of: update skill, update test assertions, provide test fixtures>

Details

<test-name>

Error: <failure from junit.xml> Location: <file:line>

&#x3C;actual line of code from the test file at the specified line number>

&#x3C;full contents of agent-metadata.md file, verbatim>

Important

Include the complete, unmodified contents of each agent-metadata.md
file in the issue body. Do NOT summarize or truncate the logs. Wrap each log in a &#x3C;details>
block with the test name as the summary.

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Open in GitHubOpen in ClawHub

Related Skills

Related by shared tags or category signals.

Coding

azure-compute

Azure VM and VMSS router for recommendations, pricing, autoscale, orchestration, connectivity troubleshooting, and capacity reservations. WHEN: Azure VM, VMSS, scale set, recommend, compare, server, website, burstable, lightweight, VM family, workload, GPU, learning, simulation, dev/test, backend, autoscale, load balancer, Flexible orchestration, Uniform orchestration, cost estimate, connect, refused, Linux, black screen, reset password, reach VM, port 3389, NSG, troubleshoot, capacity reservation, CRG, reserve VMs, guarantee capacity, pre-provision capacity, CRG association, CRG disassociation.

Repository Source
266.6K764Microsoft
Coding

azure-cloud-migrate

Assess and migrate cross-cloud workloads to Azure with migration reports and code conversion. Supports Lambda→Functions, Fargate→Container Apps, Kubernetes→Container Apps, Cloud Run→Container Apps. WHEN: migrate Lambda to Functions, AWS to Azure, Lambda assessment, convert serverless, readiness report, from AWS, from GCP, Cloud Run migration, Fargate to ACA, ECS to Container Apps, Kubernetes to ACA, GKE to Azure, EKS to Container Apps.

Repository Source
266.5K764Microsoft
Coding

azure-messaging

Troubleshoot and resolve issues with Azure Messaging SDKs for Event Hubs and Service Bus. Covers connection failures, authentication errors, message processing issues, and SDK configuration problems. WHEN: event hub SDK error, service bus SDK issue, messaging connection failure, AMQP error, event processor host issue, message lock lost, message lock expired, lock renewal, lock renewal batch, send timeout, receiver disconnected, SDK troubleshooting, azure messaging SDK, event hub consumer, service bus queue issue, topic subscription error, enable logging event hub, service bus logging, eventhub python, servicebus java, eventhub javascript, servicebus dotnet, event hub checkpoint, event hub not receiving messages, service bus dead letter, batch processing lock, session lock expired, idle timeout, connection inactive, link detach, slow reconnect, session error, duplicate events, offset reset, receive batch.

Repository Source
266.4K764Microsoft
Coding

azure-hosted-copilot-sdk

Build, deploy, modify GitHub Copilot SDK apps on Azure. MANDATORY when codebase contains @github/copilot-sdk or CopilotClient — use this skill instead of azure-prepare. PREFER OVER azure-prepare when codebase contains copilot-sdk markers. WHEN: copilot SDK, @github/copilot-sdk, copilot-powered app, deploy copilot app, add feature, modify copilot app, BYOM, bring your own model, CopilotClient, createSession, sendAndWait, azd init copilot. DO NOT USE FOR: general web apps without copilot SDK (use azure-prepare), Copilot Extensions, Foundry agents (use microsoft-foundry).

Repository Source
266.4K764Microsoft