file-test-bug Skill
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 Published by microsoft in GitHub-Copilot-for-Azure.
Decision snapshot
Is this a fit?
Testing, Writing, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
2 months ago · NOASSERTION license
No specific cautions were detected. Review the source and requested permissions before installing.
What is file-test-bug Skill?
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 Published by microsoft in GitHub-Copilot-for-Azure. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Testing
- Writing
- Testing use cases
- Writing use cases
Declared skill metadata
- Declared author: Microsoft
- Declared license: MIT
- Source file: .github/skills/file-test-bug/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use file-test-bug Skill
- Use it for testing.
- Use it for writing.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/GitHub-Copilot-for-Azure
- Skill file: .github/skills/file-test-bug/SKILL.md
What it does
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
Skill instructions
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 1. Ask user for skill name if not provided 2. Parse tests/reports/junit.xml for failures matching the skill 3. Find test run directory (specified or most recent with matching logs) 4. Read agent-metadata.md from tests/reports/test-run-<timestamp/<skillname-<testname/ 5. For each failure, read the actual line of code from the test file using the location (file:line) from junit.xml 6. 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 p
Verified compatibility and discovery
Frequently asked questions
What is file-test-bug?
file-test-bug is a open-source AI agent skill with Copy skill directory. 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
Who is file-test-bug best for?
file-test-bug is best for reusing agent instructions, scripts, and references, testing workflows, writing workflows.
How do I install file-test-bug?
Install or run file-test-bug using Copy skill directory. Check file-test-bug for the latest setup command.
Is file-test-bug actively maintained?
file-test-bug may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
