File test bug

Skill ulpi-io/plugin-marketplace/plugins/microsoft/skills/file-test-bug

A curated collection of 7,800+ agent skills for Claude Desktop, sourced from skills.sh

Install

npx -y skills add ulpi-io/plugin-marketplace --skill file-test-bug

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

File a GitHub issue for local integration test failures. TRIGGERS: file test bug, report test failure, create bug for test, integration test failed, test failure issue, junit failure

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.5 KB, as published. Nobody here has run it

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.