gstack-investigate
Systematic root-cause debugging for OPC work. Use when there is a bug, crash, regression, failing command, flaky behavior, provider issue, or unexplained output. Requires evidence before fixes.
소스 정보
- 저장소
- LING71671/Open-ClaudeCode
- 최근 소스 활동
- 2026년 6월 8일 18:43
- 감지된 SKILL.md 언어
- 영어
- 스타
- 961
- 포크
- 1,217
설치 방법
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
소스 파일 검토
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
SKILL.md 표시 중
SKILL.md
소스 지침 · 읽기 전용 미리보기- name
- gstack-investigate
- description
- Systematic root-cause debugging for OPC work. Use when there is a bug, crash, regression, failing command, flaky behavior, provider issue, or unexplained output. Requires evidence before fixes.
- allowed-tools
- ["Read","Grep","Glob","Bash","Edit","Write"]
# gstack-investigate
Use this skill to diagnose before fixing.
## Workflow
1. State the observed symptom and the expected behavior.
2. Reproduce the issue with the smallest command, UI flow, fixture, or log slice available.
3. Trace the relevant path through the code before proposing a fix.
4. Form at least three plausible causes.
5. Test the causes with targeted checks, logs, assertions, or isolated commands.
6. Pick the cause with the strongest evidence.
7. Apply the smallest fix that addresses that cause.
8. Re-run the original reproduction and one nearby regression check.
## Rules
- Do not fix before reproduction or strong evidence.
- If one attempted fix fails, record why and try a different strategy.
- Prefer direct runtime evidence: command output, logs, API responses, persisted state, or failing tests.
- Keep unrelated refactors out of the fix.
## Output
Report:
- Symptom
- Root cause
- Fix
- Verification command or manual check
- Residual risk
GitHub에서 보기