bug-triage-evidence — community bug-triage-evidence, IPIN-Examples, community, ide skills, Claude Code, Cursor, Windsurf

v1.0.0
GitHub

About this Skill

Ideal for Debugging Agents requiring systematic bug triage and evidence packaging capabilities. Example codes for the book "Principles of Indoor Positioning and Indoor Navigation"

IPNL-POLYU IPNL-POLYU
[0]
[0]
Updated: 3/3/2026

Agent Capability Analysis

The bug-triage-evidence skill by IPNL-POLYU is an open-source community AI agent skill for Claude Code and other IDE workflows, helping agents execute tasks with better context, repeatability, and domain-specific guidance.

Ideal Agent Persona

Ideal for Debugging Agents requiring systematic bug triage and evidence packaging capabilities.

Core Value

Empowers agents to reproduce and document bugs efficiently using markdown formatted README files and organized folder structures, streamlining the handoff process to other engineers and facilitating collaboration through clear bug reports and reproducible test cases.

Capabilities Granted for bug-triage-evidence

Reproducing and documenting simulation errors
Creating comprehensive bug reports for engineering teams
Organizing and packaging evidence for failed tests

! Prerequisites & Limits

  • Requires filesystem access for creating bug bundles
  • Assumes familiarity with markdown formatting for README files
Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

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.

SKILL.md
Readonly

Bug triage & evidence packaging

Use this skill when:

  • A simulation result looks wrong, plots mismatch expected figures, or a test fails.
  • You need to hand off a clear bug report to another engineer.

Workflow

  1. Reproduce
  • Write the minimal reproduction steps (command, script entrypoint, seed if relevant).
  • Capture expected vs actual behavior in 1–3 bullets.
  1. Create a bug bundle in .dev/ Create a folder:
  • .dev/bug-<short-slug>/ Include:
  • README.md containing:
    • symptoms
    • reproduction steps
    • expected vs actual
    • suspected root cause (if any)
    • fix summary + verification steps
  • Any logs / short diffs / notes needed to validate.
  1. Figures
  • If the bug is chapter-specific: save plots in chX_*/figs/
  • If it's general debugging evidence: also copy or link into .dev/bug-<slug>/
  1. Update chapter README when relevant If the bug affects a chX_*/README.md:
  • Add a short student-centric note:
    • what was wrong
    • what was fixed
    • how to run the corrected example
    • reference the figure files you saved in chX_*/figs/
  1. Verification
  • Add/adjust tests under tests/ to prevent regression.
  • Re-run the minimal reproduction + full test suite if reasonable.

Output standard

A reviewer should be able to:

  • reproduce in <5 minutes
  • see the mismatch in one figure
  • see the fix rationale in one page

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?

Ideal for Debugging Agents requiring systematic bug triage and evidence packaging capabilities. Example codes for the book "Principles of Indoor Positioning and Indoor Navigation"

How do I install bug-triage-evidence?

Run the command: npx killer-skills add IPNL-POLYU/IPIN-Examples. 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 and documenting simulation errors, Creating comprehensive bug reports for engineering teams, Organizing and packaging evidence for failed tests.

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 files.

How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add IPNL-POLYU/IPIN-Examples. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use bug-triage-evidence immediately in the current project.

Related Skills

Looking for an alternative to bug-triage-evidence or another community skill for your workflow? Explore these related open-source skills.

View All

widget-generator

Logo of f
f

f.k.a. Awesome ChatGPT Prompts. Share, discover, and collect prompts from the community. Free and open source — self-host for your organization with complete privacy.

149.6k
0
AI

flags

Logo of vercel
vercel

flags is a Next.js feature management skill that enables developers to efficiently add or modify framework feature flags, streamlining React application development.

138.4k
0
Browser

zustand

Logo of lobehub
lobehub

The ultimate space for work and life — to find, build, and collaborate with agent teammates that grow with you. We are taking agent harness to the next level — enabling multi-agent collaboration, effortless agent team design, and introducing agents as the unit of work interaction.

72.8k
0
AI

data-fetching

Logo of lobehub
lobehub

The ultimate space for work and life — to find, build, and collaborate with agent teammates that grow with you. We are taking agent harness to the next level — enabling multi-agent collaboration, effortless agent team design, and introducing agents as the unit of work interaction.

72.8k
0
AI