skills.rest
pillip
pillipCOMMUNITY
Explore all skills by this author →
GitHub

diagnose

Diagnose bugs from logs or reproduction steps and create GitHub Issues and PRs.

11|Updated Feb 18, 2026
Search Tags:#debugging#diagnose#pull-request#reproduction-steps#bug#github-issue#error-logs
One-click install
npx skills add https://github.com/pillip/claude-dev-kit --skill diagnose-pillip
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: diagnose
Source: https://github.com/pillip/claude-dev-kit/tree/main/skills/diagnose
Command: npx skills add https://github.com/pillip/claude-dev-kit --skill diagnose-pillip

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Analyze error logs or reproduction steps to identify root causes and streamline bug triage from detection to resolution.

Core Features & Use Cases

  • Error analysis: parse logs, stack traces, and reproduction steps to hypothesize root causes.
  • Automated triage: generate a GitHub Issue and PR scaffold to capture context and proposed changes.
  • End-to-end workflow: supports context-aware fixes across projects, with checkpoints and reviews.

Quick Start

Provide an error description or stack trace and reproduction steps to trigger the issue, and the skill will generate a tracked GH Issue and PR.

Frequently Asked Questions about diagnose

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

FAQPage Schema
How do I diagnose bugs from error logs and reproduction steps automatically?▼

To diagnose bugs automatically, you can provide error logs, stack traces, and reproduction steps to trigger root cause analysis. The system parses these inputs to hypothesize root causes and streamline bug triage from detection to resolution.

Can I automatically create a GitHub issue and pull request from a stack trace?▼

Yes, you can automatically create a GitHub issue and pull request from a stack trace. The automated triage feature generates a GitHub Issue and PR scaffold to capture context and proposed changes for remediation tracking.

What is the best way to track bug remediation across code reviews and sprints?▼

Tracking bug remediation across code reviews and sprints requires an end-to-end workflow with checkpoints. This approach supports context-aware fixes, multi-phase validation, and integrates with sprint workflows for traceability.

Do I need to provide reproduction steps to identify the root cause of a bug?▼

Providing reproduction steps is highly recommended to identify the root cause of a bug accurately. The diagnostic process parses logs, stack traces, and reproduction steps to hypothesize root causes effectively.

Does automated bug triage support context-aware fixes with checkpoints?▼

Automated bug triage supports context-aware fixes with checkpoints and reviews. This end-to-end workflow ensures fixes are validated across projects, satisfying project context checks throughout the remediation process.

Why apply fixes and generate a PR scaffold during bug triage?▼

Applying fixes and generating a PR scaffold during bug triage captures context and proposed changes directly. This automated triage creates a GitHub Issue and PR to track remediation across issues and code reviews seamlessly.

Related Skills

Explore More Software Engineering Skills→
jk278jk278

debugging-assistant

Diagnose software bugs from stack traces and error logs.

Community
Advanced
vultukvultuk
1

auto-issue-fixer

Automate GitHub issue triage, TDD implementation, PR creation, and review completion.

Community
Advanced
kirich1409kirich1409
23

bugfix-flow

Orchestrate end-to-end bug fixes across diagnosis, planning, implementation, regression testing, and PR workflows.

Community
Advanced
zhu637882-stackzhu637882-stack

investigate

Guides users through a four-phase workflow to identify root causes of software failures.

Community
Advanced