Creates a GitHub issue in microsoft/github-copilot-for-azure for integration test failures.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionfile-test-bugExecute the skills CLI command in your project's root directory to begin installation:
Fetches file-test-bug from microsoft/github-copilot-for-azure and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate file-test-bug. Access via /file-test-bug in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
180
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
180
stars
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>
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.
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
microsoft/github-copilot-for-azure
cexll/myclaude
github/awesome-copilot
github/awesome-copilot
dotnet/skills
aj-geddes/useful-ai-prompts
Solid pick for teams standardizing on skills: file-test-bug is focused, and the summary matches what you get after install.
file-test-bug is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Useful defaults in file-test-bug — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Registry listing for file-test-bug matched our evaluation — installs cleanly and behaves as described in the markdown.
Useful defaults in file-test-bug — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
file-test-bug fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Registry listing for file-test-bug matched our evaluation — installs cleanly and behaves as described in the markdown.
Useful defaults in file-test-bug — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Registry listing for file-test-bug matched our evaluation — installs cleanly and behaves as described in the markdown.
file-test-bug has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 34