file-test-bug

Name: file-test-bug
Author: microsoft

Create a GitHub issue from local integration test failures.

Stars

★ 232

Source

GitHub

Updated

2026-07-13

// securityLow risk

Prompt only, no code
Open source
Community-trusted· 232

Running security audit…

Credentials
Network egress
Code execution
Data access
Supply chain

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "file-test-bug" skill from askskill:
1. Download https://raw.githubusercontent.com/microsoft/GitHub-Copilot-for-Azure/main/.github/skills/file-test-bug/SKILL.md
2. Save it as ~/.claude/skills/file-test-bug/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// examples

File an integration test failure bug

Prompt

Based on the following local integration test failure logs, extract the key details and draft a GitHub issue including a title, summary, reproduction steps, expected result, actual result, and relevant log snippets:

[paste test logs]

Expected

A well-structured GitHub issue draft that the team can submit and investigate directly.

Create an issue from a JUnit failure report

Prompt

I have a JUnit failure report. Turn the failed test cases, exception details, impact, and likely reproduction steps into a GitHub bug report in Markdown:

[paste JUnit report]

Expected

A Markdown bug report highlighting failed cases, error causes, and debugging clues.

Summarize multiple test failures into one bug

Prompt

Below are multiple failures from the same local integration test run. Determine whether they belong to the same issue and generate a consolidated GitHub issue with affected modules, shared symptoms, and attachment recommendations:

[paste multiple failure records]

Expected

A consolidated issue draft that helps the team avoid duplicates and find the root cause faster.

// docs

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>
  ```typescript
  <actual line of code from the test file at the specified line number>

<details> <summary>agent-metadata.md</summary>

</details> ```

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 <details> block with the test name as the summary.