Tyler-R-Kendrick/file-test-bug
.agent/skills/file-test-bug/SKILL.md
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 --global
skillsauthnpx skillsauth add Tyler-R-Kendrick/agent-skills file-test-bugInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 15, 2026, 10:50 PM30.8s1 file scanned
SKILL.md
- name:
- file-test-bug
- description:
- 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
File Test Bug
Creates a GitHub issue in microsoft/github-copilot-for-azure for integration test failures.
Input
- Skill name (required): e.g.,
azure-role-selector,appinsights-instrumentation - Test run (optional): Timestamp of test run. Defaults to most recent with logs for the skill.
Steps
- Ask user for skill name if not provided
- Parse
tests/reports/junit.xmlfor failures matching the skill - Find test run directory (specified or most recent with matching logs)
- Read
agent-metadata.mdfromtests/reports/test-run-<timestamp>/<skillname>-<testname>/ - 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:
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> ```Important
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.
Related Skills
Tyler-R-Kendrick/design-system
tools
VerifiedTrustedCommunity
Use when building or maintaining a design system — the coordinated set of design tokens, component libraries, documentation, and tooling that ensures visual and behavioral consistency across products. USE FOR: design system architecture, choosing token formats vs component frameworks, connecting Figma to code, design-to-development workflows, multi-platform consistency DO NOT USE FOR: specific token authoring (use design-tokens), Figma workflows (use figma), component cataloging (use storybook), token transformation (use style-dictionary), cross-framework components (use mitosis)
10SKILL.mdUpdated Jun 10, 2026
Tyler-R-Kendrick/x402
tools
VerifiedTrustedCommunity
Use when implementing the x402 protocol for HTTP-native micropayments. Covers server middleware, client payment flows, facilitator integration, and stablecoin payments for APIs and AI agents. USE FOR: API micropayments, monetizing endpoints, stablecoin HTTP payments, automated agent payments for API access DO NOT USE FOR: full commerce flows with cart/checkout (use ap2), agent communication (use a2a), tool integration (use mcp)
10SKILL.mdUpdated Jun 10, 2026
Tyler-R-Kendrick/mcp
tools
VerifiedTrustedCommunity
Use when implementing or integrating with the Model Context Protocol (MCP) for AI tool servers, resources, prompts, and context management. USE FOR: building MCP tool servers, exposing resources to agents, prompt templates, connecting agents to external APIs DO NOT USE FOR: agent-to-agent communication (use a2a), interactive UI rendering (use mcp-apps), agent payments (use x402 or ap2)
10SKILL.mdUpdated Jun 10, 2026
Tyler-R-Kendrick/mcp-apps
tools
VerifiedTrustedCommunity
Use when building MCP Apps that serve interactive UI from MCP servers. Covers the ui:// URI scheme, HTML rendering in sandboxed iframes, and bidirectional communication between UI and host. USE FOR: rich UI in agent conversations, interactive dashboards from MCP servers, sandboxed iframe rendering DO NOT USE FOR: basic tool responses without UI (use mcp), agent communication (use a2a), full web applications
10SKILL.mdUpdated Jun 10, 2026