사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/withastro/astro --skill triage시작 전 확인
- 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
- 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.
Triage
Triage a bug report end-to-end: reproduce the bug, diagnose the root cause, verify whether the behavior is intentional, and attempt a fix.
General Rules
Do not get stuck on infrastructure problems. If a server won't start, a port is blocked, or a tool is unavailable in the CI environment — bail out after 2 attempts and write your report with the data you already have. Looping on server restarts or missing CLI tools wastes your entire time budget. A partial report with solid findings is infinitely more valuable than no report because you ran out of time fighting a stale process.
Input
You need either:
issueTitleandissueBodyprovided in args (preferred — use these directly as the bug report), OR- A GitHub issue number or URL mentioned in the conversation (use
gh issue viewto fetch details)
If a triageDir is provided in args, use that as the working directory for the triage. Otherwise, default to triage/gh-<issue_number> (if you have an issue number) or triage/current.
Step 1: Reproduce
Read and follow reproduce.md. Use a subagent for this step to isolate context.
After completing reproduction, check the result:
- If the issue was skipped (host-specific, unsupported version, etc.) — skip to Output.
- If the issue was not reproducible — skip to Output.
- If the issue was reproduced — continue to Step 2.
Step 2: Diagnose
Read and follow diagnose.md. Use a subagent for this step to isolate context.
After completing diagnosis, check your confidence:
- If confidence is low — skip to Output.
- If confidence is medium or high — continue to Step 3.
Step 3: Verify
Read and follow verify.md. Use a subagent for this step to isolate context.
After completing verification, check the verdict:
- If the verdict is intended-behavior — skip to Output. The issue is not a bug; do not attempt a fix.
- If the verdict is bug or unclear — continue to Step 4.
Step 4: Fix
Read and follow fix.md. Use a subagent for this step to isolate context.
Whether the fix succeeds or fails, continue to Output.
Output
After completing the triage (or exiting early), return your structured results so the orchestrator can post a comment and manage labels.
