One-click install
npx skills add https://github.com/oci-ai-incubations/ai-accelerator-starter-packs --skill bug-tracker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bug-tracker
Source: https://github.com/oci-ai-incubations/ai-accelerator-starter-packs/tree/main/.claude/skills/bug-tracker
Command: npx skills add https://github.com/oci-ai-incubations/ai-accelerator-starter-packs --skill bug-tracker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintains a centralized, up-to-date BUGS.md to capture discovered bugs, their symptoms, root causes, and resolutions, ensuring visibility and consistent triage across teams.

Core Features & Use Cases

  • Log new bugs with a structured template to capture symptoms, impact, and a proposed fix.
  • Mark bugs as fixed by updating status, date, and resolution details, linking to PRs or commits.
  • Review and prioritize open bugs during triage, sprint planning, and release readiness.

Quick Start

Log a new bug with a concise description to append an entry to BUGS.md.

Frequently Asked Questions about bug-tracker

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I track bugs and document issues in a centralized file?

To track bugs centrally, log symptoms, root causes, and resolutions into a structured BUGS.md file. This enforces consistent triage and visibility across development teams by appending entries with impact details and proposed fixes.

What is the best way to log a new bug for triage and sprint planning?

The best way to log a new bug for triage is to apply a structured template that captures symptoms, impact, and proposed fixes within BUGS.md. This ensures entries are consistently formatted for review and release readiness.

Can I mark bugs as fixed and link them to specific commits in BUGS.md?

Yes, you can mark bugs as fixed by updating the status, date, and resolution details in BUGS.md. The structured format allows you to link resolutions directly to specific PRs or commits for complete traceability.

Does a BUGS.md file work for documenting root cause and resolution details?

A BUGS.md file works effectively for documenting root causes and resolutions by maintaining a standardized log. It captures discovered bugs and their fixes to ensure visibility and consistent triage across project workstreams.

What should I include in a bug report template for issue tracking?

A bug report template for issue tracking should include the symptom description, impact assessment, root cause, and resolution details. Structuring these elements in BUGS.md ensures clear visibility and efficient triage during release management.

How do I review open bugs during release readiness and sprint planning?

Review open bugs during release readiness by consulting the centralized BUGS.md file to prioritize unresolved issues. This structured log supports triage and sprint planning by maintaining clear visibility into symptoms and proposed fixes.