my-trouble-detect

Collect and analyze logs, changes, and environment to identify coding error root causes.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/jjub0217/claude-code-skills --skill my-trouble-detect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: my-trouble-detect
Source: https://github.com/jjub0217/claude-code-skills/tree/main/skills/my-trouble-detect
Command: npx skills add https://github.com/jjub0217/claude-code-skills --skill my-trouble-detect

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

에러/삽질 발생 시 컨텍스트를 자동 수집하고 분석해 원인 파악과 해결 방향 제안을 빠르게 제공합니다.

Core Features & Use Cases

  • 3개 병렬 에이전트로 에러 로그, 변경 이력, 환경 정보를 수집합니다.
  • 패턴 분석 에이전트가 과거 트러블과 비교해 반복 패턴을 식별하고 해결 방향을 제시합니다.
  • 트러블슈팅 리포트를 자동으로 생성하여 나중에 패턴 분석에 활용할 수 있습니다.
  • 사용 예시: 빌드 실패 시 에러 로그와 환경 정보를 바탕으로 원인을 제시하고 다음 조치를 안내합니다.

Quick Start

Invoke the skill with /my-trouble-detect to start a troubleshooting session.

Frequently Asked Questions about my-trouble-detect

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

FAQPage Schema
How do I find the root cause of a build failure from error logs and git diffs?

To find the root cause of a build failure, automated troubleshooting ingests error logs, git diffs, and environment details to analyze diagnostic context and propose actionable fixes.

What is automated context collection for debugging runtime errors?

Automated context collection for debugging uses parallel agents to gather error logs, change histories, and environment information, identifying root causes of runtime errors quickly.

How to troubleshoot deployment issues using environment details and change history?

Troubleshoot deployment issues by collecting and analyzing environment details and change histories in parallel, applying pattern analysis against past troubles to guide actionable fixes.

Can I use automated trouble detection for CI-CD pipeline errors?

Yes, automated trouble detection applies to CI-CD pipeline errors by ingesting error messages and environment variables to identify root causes and propose real-world troubleshooting steps.

Does automated troubleshooting work without external dependencies for error logging?

Automated troubleshooting operates without external dependencies, collecting error logs and diagnostic context directly to analyze build failures and runtime errors independently.

What is the best way to analyze recurring error patterns in software engineering?

The best way to analyze recurring error patterns is using a pattern analysis agent that compares current diagnostic context against past generated troubleshooting reports to identify repeat issues.