skills.rest
ArtyMcLabin
ArtyMcLabinCOMMUNITY
Explore all skills by this author →
Website𝕏@Arty_McLabinGitHub

issue-handler

Diagnose a GitHub issue by querying logs, reproducing failures, and preparing a CTO handoff.

8|1|Updated Aug 5, 2025
Search Tags:#logs#GitHub#evidence#handoff#reproduction#issue-diagnosis
One-click install
npx skills add https://github.com/ArtyMcLabin/ClaudeCode-global-config --skill issue-handler
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: issue-handler
Source: https://github.com/ArtyMcLabin/ClaudeCode-global-config/tree/main/skills/issue-handler
Command: npx skills add https://github.com/ArtyMcLabin/ClaudeCode-global-config --skill issue-handler

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Issue Handler provides an evidence-based investigation workflow to determine why a GitHub issue is failing, by querying logs, reproducing the issue, collecting evidence, and preparing a CTO handoff.

Core Features & Use Cases

  • Per-issue diagnosis: Analyzes a single issue end-to-end with deterministic steps.
  • Evidence-focused: Collects logs, reproduction results, and context for CTO review.
  • Hand-off ready: Packages findings for CTO agent to implement fixes.

Quick Start

Example: Diagnose issue #123 and prepare a CTO handoff package with logs, reproduction steps, and evidence.

Frequently Asked Questions about issue-handler

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

FAQPage Schema
How do I diagnose a GitHub issue using logs and reproduction tests?▼

Diagnose a GitHub issue by querying logs, reproducing the failure with deterministic test harnesses, collecting evidence, and packaging a handoff for CTO review. This workflow applies to individual issues across repositories.

What is evidence-driven issue diagnosis for GitHub repositories?▼

Evidence-driven issue diagnosis determines why a GitHub issue is failing by collecting logs, reproduction results, and context. It packages these findings into an auditable diagnosis ready for CTO review and implementation.

Do I need an auditable logging pipeline to reproduce GitHub issues?▼

Yes, reproducing GitHub issues requires an auditable logging pipeline and deterministic test harnesses. These prerequisites ensure the collected evidence is reliable and the failure reproduction is accurate for CTO handoff.

Can I analyze multiple GitHub issues simultaneously across different repositories?▼

No, this issue diagnosis workflow analyzes a single GitHub issue end-to-end. It applies to individual issues across repositories, sequentially collecting evidence and preparing a packaged diagnosis for CTO review.

What's the best way to prepare a GitHub issue handoff for a CTO agent?▼

Prepare a CTO handoff by querying logs, reproducing the failure, and gathering evidence into a packaged diagnosis. This end-to-end workflow ensures the CTO agent receives auditable context to implement fixes.

Related Skills

Explore More Software Engineering Skills→
markus41markus41
18

harness-pipeline

Execute and monitor Harness CI/CD pipelines with integrated Jira issue tracking and updates.

Community
Intermediate
ZaxbyHubZaxbyHub
437

issue-tracer

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

Official
Advanced
sd0xdevsd0xdev
187

issue-analyze

Analyze GitHub issues to produce structured problem diagnoses and investigation plans.

Community
Intermediate
lapc506lapc506
4

Error Tracking & Crash Reporting

Implement Sentry and Firebase Crashlytics error tracking for Flutter applications.

Community
Advanced