Skip to main content
Back to the directory
microsoft/github-copilot-for-azureSoftware EngineeringFrontend and Design

file-test-bug

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

SkillJury keeps community verdicts, source metadata, and external repository signals in separate lanes so ranking data never pretends to be a review.

SkillJury verdict
Pending

No approved reviews yet

Would recommend
Pending

Waiting on enough review volume

Install signal
1

Weekly or total install activity from catalog data

Sign in to review
0 review requests
Install command
npx skills add https://github.com/microsoft/github-copilot-for-azure --skill file-test-bug
SkillJury does not have enough approved reviews to publish a community verdict yet. Source metadata and repository proof are still available above.
SkillJury Signal Summary

As of Apr 30, 2026, file-test-bug has 1 weekly installs, 0 community reviews on SkillJury. Community votes currently stand at 0 upvotes and 0 downvotes. Source: microsoft/github-copilot-for-azure. Canonical URL: https://skills.sh/microsoft/github-copilot-for-azure/file-test-bug.

Security audits
Gen Agent Trust HubPASS
SocketPASS
SnykFAIL
About this skill
Creates a GitHub issue in microsoft/github-copilot-for-azure for integration test failures. 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 block with the test name as the summary. - 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. - 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- / - / - 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 :

Source description provided by the upstream listing. Community review signal and install context stay separate from this narrative layer.

Community reviews

Latest reviews

No community reviews yet. Be the first to review.

Browse this skill in context
FAQ
What does file-test-bug do?

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

Is file-test-bug good?

file-test-bug does not have approved reviews yet, so SkillJury cannot publish a community verdict.

Which AI agents support file-test-bug?

file-test-bug currently lists compatibility with Skills CLI.

Is file-test-bug safe to install?

file-test-bug has been scanned by security audit providers tracked on SkillJury. Check the security audits section on this page for detailed results from Socket.dev and Snyk.

What are alternatives to file-test-bug?

Skills in the same category include grimoire-morpho-blue, conversation-memory, second-brain-ingest, zai-tts.

How do I install file-test-bug?

Run the following command to install file-test-bug: npx skills add https://github.com/microsoft/github-copilot-for-azure --skill file-test-bug

Related skills

More from microsoft/github-copilot-for-azure

Related skills

Alternatives in Software Engineering