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
Creates a GitHub issue in microsoft/github-copilot-for-azure for integration test failures.
azure-rbac, appinsights-instrumentationtests/reports/junit.xml for failures matching the skillagent-metadata.md from tests/reports/test-run-<timestamp>/<skillname>-<testname>/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><full contents of agent-metadata.md file, verbatim>
</details> ```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.
cc82eeb
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.