skills.rest
ZaxbyHub
ZaxbyHubOFFICIAL
Explore all skills by this author →
GitHub

issue-tracer

Trace GitHub issues to root cause and validate fixes with evidence.

437|45|Updated Jan 27, 2026
Search Tags:#code review#root cause analysis#github issues#regression testing#bug tracing#evidence capture#pr closure
One-click install
npx skills add https://github.com/ZaxbyHub/opencode-swarm --skill issue-tracer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: issue-tracer
Source: https://github.com/ZaxbyHub/opencode-swarm/tree/main/.agents/skills/issue-tracer
Command: npx skills add https://github.com/ZaxbyHub/opencode-swarm --skill issue-tracer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

This Skill eliminates the risk of unverified, root-cause-unproven bug fixes that lead to recurring issues, broken production behavior, and wasted engineering time by enforcing a strict evidence-first tracing and validation workflow for GitHub issues, bug reports, regressions, and failing tests.

Core Features & Use Cases

  • End-to-end issue tracing: Takes a reported issue from intake to PR closure with full, auditable evidence capture at every phase.
  • Structured root-cause localization: Uses trace-driven, semantic, and hypothesis-driven playbooks to pinpoint exact code locations and triggering conditions for bugs.
  • Gated quality checks: Includes independent critic reviews, implementation reviews, and final critic gates to ensure fixes address root causes, not just visible symptoms.
  • Use Case: Engineering teams working on OpenCode or similar AI coding tools can use this Skill to resolve high-risk bugs, regressions, or failing tests with production-ready fixes that pass all required validation and invariant checks.

Quick Start

Use the issue-tracer skill to investigate the linked GitHub bug report, identify the exact root cause, and prepare a verified fix with full evidence and test coverage.

Frequently Asked Questions about issue-tracer

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

FAQPage Schema
How do I perform evidence-first bug tracing for GitHub issues?▼

Evidence-first bug tracing requires taking a reported issue from intake to PR closure with full, auditable evidence capture at every phase. This enforces reproducible issue reproduction, precise code localization, and invariant-aware PR closure to ensure verified production fixes.

What is the best way to pinpoint the root cause of a regression or failing test?▼

The best way to pinpoint the root cause of a regression is using trace-driven, semantic, and hypothesis-driven playbooks. This structured root-cause localization identifies exact code locations and triggering conditions for bugs rather than just addressing visible symptoms.

How do I ensure my bug fixes pass independent code review before PR closure?▼

To ensure bug fixes pass independent code review, enforce gated quality checks throughout the workflow. This includes independent critic reviews, implementation reviews, and final critic gates to verify that fixes address root causes and maintain production safety.

Can I use this structured bug tracing workflow with OpenCode or similar AI coding tools?▼

Yes, this structured bug tracing workflow applies to engineering workflows for codebases using OpenCode or similar AI coding tools. It resolves high-risk bugs, regressions, or failing tests with production-ready fixes that pass all required validation and invariant checks.

Why do unverified bug fixes lead to recurring issues in production?▼

Unverified bug fixes lead to recurring issues because they lack root-cause proof and auditable evidence capture. Without strict evidence-first tracing and validation, fixes often address visible symptoms rather than the underlying trigger, resulting in broken production behavior.

Related Skills

Explore More Software Engineering Skills→
sQVesQVe

debug-issue

Diagnose bugs by tracing evidence and generating a BR issue template.

Community
Advanced
bobmatnycbobmatnyc
68

bug-fix

Guide bug fix verification through reproduction, root cause analysis, and regression testing.

Community
Advanced
ZaxbyHubZaxbyHub
437

swarm

Enforces a gated, parallel swarm workflow for AI-generated code review and validation.

Official
Advanced
withkynamwithkynam
1.1k

vc-debug

Trace root causes of bugs and failures through a four-phase investigation workflow.

Community
Advanced