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
Install with Tessl CLI
npx tessl i github:microsoft/github-copilot-for-azure --skill file-test-bug93
Does it follow best practices?
Evaluation — 81%
↑ 2.02xAgent success when using this skill
Validation for skill structure
Pre-diagnosis and root cause workflow
Reads junit.xml
50%
100%
Finds most recent test run
62%
100%
Reads agent-metadata.md path
100%
100%
Reads agent-metadata.md for test 2
100%
100%
Extracts test 1 assertion line
0%
0%
Extracts test 2 assertion line
0%
0%
Root cause categorized
0%
50%
2-3 sentences per failure
0%
50%
Covers both failures
100%
100%
Suggested fix category
0%
100%
Without context: $0.1950 · 57s · 8 turns · 11 in / 3,043 out tokens
With context: $0.3241 · 1m 18s · 15 turns · 272 in / 4,096 out tokens
GitHub issue structure and labeling
Correct tool name
0%
0%
Owner: microsoft
100%
100%
Repo: github-copilot-for-azure
100%
100%
Title format
0%
100%
Label: bug
100%
100%
Label: integration-test
0%
100%
Failed Tests section
0%
100%
Diagnosis section
0%
100%
Suggested Fix section
70%
100%
Details section with location
0%
100%
TypeScript code block
100%
100%
Without context: $0.2263 · 1m 4s · 10 turns · 15 in / 4,166 out tokens
With context: $0.2744 · 1m 1s · 12 turns · 15 in / 4,003 out tokens
Agent metadata verbatim inclusion
Test 1 metadata present
100%
100%
Test 2 metadata present
100%
100%
Test 1 metadata verbatim
0%
100%
Test 2 metadata verbatim
0%
100%
Details blocks used
0%
100%
Details summary is test name
0%
0%
No truncation
100%
100%
Without context: $0.2042 · 59s · 9 turns · 14 in / 2,729 out tokens
With context: $0.3428 · 1m 23s · 15 turns · 18 in / 4,873 out tokens
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.