bug-report
Automates the bug reporting process for the Phoenix Command Center, providing root cause analysis and GitHub issue creation.
Install
mkdir -p .claude/skills/bug-report && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/10297" && unzip -o skill.zip -d .claude/skills/bug-report && rm skill.zipInstalls to .claude/skills/bug-report
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Investigate a bug and create a high-quality GitHub bug issue with reproducible steps and code-level findings for the Command Center extension. Use when user asks to report a bug, file an issue, document a regression, or write an investigation-backed bug report.Key capabilities
- →Reproduce bugs
- →Locate code paths
- →Analyze root causes
- →File GitHub issues
How it works
It reproduces the bug, analyzes the code, and uses GitHub tools to file a detailed report.
Inputs & outputs
When to use bug-report
- →Documenting extension regressions
- →Reporting bugs in Phoenix Command Center
- →Creating reproducible bug reports for developers
About this skill
Bug Report — Phoenix Command Center
Repo Context
| Field | Value |
|---|---|
| Repo | rivie13/Phoenix-Agentic-VSCode-CommandCenter |
| Owner | rivie13 |
| Visibility | Public |
| Stack | VS Code Extension · TypeScript CommonJS · vitest |
Investigation workflow
- Reproduce the bug — identify exact steps, extension commands, or webview interactions
- Locate the relevant code path in
src/(extension host) ormedia/(webview) - Read the source to understand the expected behavior
- Identify the root cause or narrow down the suspect area
- Search for related issues using GitHub MCP tools
- Write the bug report issue
CRITICAL — Use GitHub MCP tools only
NEVER use gh CLI. Always use:
mcp_github_github_issue_write— create the issuemcp_github_github_search_issues— check for duplicatesmcp_github_github_list_issues— list open issues
Load tools first:
tool_search_tool_regex({ pattern: "mcp_github" })
Bug report template
## Bug Description
<clear one-line summary>
## Steps to Reproduce
1. <step>
2. <step>
3. <step>
## Expected Behavior
<what should happen>
## Actual Behavior
<what actually happens>
## Code-Level Findings
- **File**: `src/...` or `media/...`
- **Function**: `handleIncomingMessage()` / `render()` etc.
- **Root cause**: <analysis>
## Environment
- VS Code version: <version>
- Extension version: 0.1.0
- OS: Windows / macOS / Linux
- Supervisor mode: workspace / embedded / direct
## Screenshots / Logs
<if applicable>
Valid areas for labels
extension, controller, webview, services, utils, jarvis, supervisor, agent, board, actions, prs, tests, docs
When not to use it
- →Non-extension bugs
Prerequisites
Limitations
- →Requires GitHub MCP tools
How it compares
It provides investigation-backed bug reports instead of simple descriptions.
Compared to similar skills
bug-report side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| bug-report (this skill) | 0 | 5mo | No flags | Intermediate |
| security-scan | 1 | 6mo | Review | Intermediate |
| dependency-upgrade | 26 | 5mo | Review | Intermediate |
| chrome-devtools | 41 | 7mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
security-scan
redpanda-data
Resolve npm dependency vulnerabilities detected by security scans.
dependency-upgrade
wshobson
Manage major dependency version upgrades with compatibility analysis, staged rollout, and comprehensive testing. Use when upgrading framework versions, updating major dependencies, or managing breaking changes in libraries.
chrome-devtools
mrgoonie
Browser automation, debugging, and performance analysis using Puppeteer CLI scripts. Use for automating browsers, taking screenshots, analyzing performance, monitoring network traffic, web scraping, form automation, and JavaScript debugging.
testing-workflow
amo-tech-ai
Comprehensive testing workflow for E2E, integration, and unit tests. Use when testing applications layer-by-layer, validating user journeys, or running test suites.
run-nx-generator
nrwl
Run Nx generators with prioritization for workspace-plugin generators. Use this when generating code, scaffolding new features, or automating repetitive tasks in the monorepo.
obsidian-performance-tuning
jeremylongshore
Optimize Obsidian plugin performance for smooth operation. Use when experiencing lag, memory issues, or slow startup, or when optimizing plugin code for large vaults. Trigger with phrases like "obsidian performance", "obsidian slow", "optimize obsidian plugin", "obsidian memory usage".