File Test Bug

microsoft/github-copilot-for-azureOfficial

If you're running integration tests for GitHub Copilot for Azure skills and need to file bugs when they fail, this automates the tedious part. Point it at your JUnit XML output and it'll parse the failures, dig through your test run logs to find the agent metadata, pull the actual failing line of code from your test files, and create a properly formatted GitHub issue in the microsoft/github-copilot-for-azure repo. The standout bit is that it requires a diagnosis before filing, forcing you (or Claude) to actually compare what the agent did versus what the test expected and suggest whether the fix belongs in the skill, the test, or the fixtures. It's opinionated about including full untruncated logs in collapsible sections, which is the right call for debugging later.

skills.sh installs: 978
GitHub stars: 217
last updated: Jun 11, 2026

View on GitHub

Install

$ npx -y skills add microsoft/github-copilot-for-azure --skill file-test-bug --agent claude-code

Installs into .claude/skills of the current project.

Files

File Test Bug

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

Input

Skill name (required): e.g., azure-ai, 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: