Killer-Skills Review
Decision support comes first. Repository text comes second.
This page remains useful for operators, but Killer-Skills treats it as reference material instead of a primary organic landing page.
Perfect for Debugging Agents needing efficient bug reproduction and reporting capabilities. Triage bugs and package reproducible evidence cleanly (.dev artifacts, chapter figures, and README updates). Use when fixing a bug or mismatch vs expected results.
Core Value
Empowers agents to create comprehensive bug bundles with minimal reproduction steps and expected vs actual behavior, utilizing Markdown files like README.md and organized folder structures like .dev/bug-<short-slug>/
Ideal Agent Persona
Perfect for Debugging Agents needing efficient bug reproduction and reporting capabilities.
↓ Capabilities Granted for bug-triage-evidence
! Prerequisites & Limits
- Requires filesystem access for creating bug bundles
- Assumes familiarity with Markdown formatting for README.md files
Why this page is reference-only
- - The underlying skill quality score is below the review floor.
Source Boundary
The section below is supporting source material from the upstream repository. Use the Killer-Skills review above as the primary decision layer.
Browser Sandbox Environment
⚡️ Ready to unleash?
Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.
FAQ & Installation Steps
These questions and steps mirror the structured data on this page for better search understanding.
? Frequently Asked Questions
What is bug-triage-evidence?
Perfect for Debugging Agents needing efficient bug reproduction and reporting capabilities. Triage bugs and package reproducible evidence cleanly (.dev artifacts, chapter figures, and README updates). Use when fixing a bug or mismatch vs expected results.
How do I install bug-triage-evidence?
Run the command: npx killer-skills add IPNL-POLYU/IPIN-Examples/bug-triage-evidence. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.
What are the use cases for bug-triage-evidence?
Key use cases include: Reproducing failed tests, Generating bug reports with expected vs actual behavior, Creating minimal reproduction steps for handoff to other engineers.
Which IDEs are compatible with bug-triage-evidence?
This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.
Are there any limitations for bug-triage-evidence?
Requires filesystem access for creating bug bundles. Assumes familiarity with Markdown formatting for README.md files.
↓ How To Install
-
1. Open your terminal
Open the terminal or command line in your project directory.
-
2. Run the install command
Run: npx killer-skills add IPNL-POLYU/IPIN-Examples/bug-triage-evidence. The CLI will automatically detect your IDE or AI agent and configure the skill.
-
3. Start using the skill
The skill is now active. Your AI agent can use bug-triage-evidence immediately in the current project.
! Reference-Only Mode
This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.
Imported Repository Instructions
The section below is supporting source material from the upstream repository. Use the Killer-Skills review above as the primary decision layer.
bug-triage-evidence
Install bug-triage-evidence, an AI agent skill for AI agent workflows and automation. Works with Claude Code, Cursor, and Windsurf with one-command setup.
