사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/enitrat/skill-issue --skill github-issue시작 전 확인
- 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
- 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.
GitHub issues
The reader is a teammate who was not in the conversation. The issue gives them a model of the problem and the system it lives in, then hands them the work. They own the solution. The issue points; it does not prescribe.
Only what matters is written. A line earns its place when the reader would get the problem wrong without it. When unsure, cut.
Title
Conventional commit format, validated by the script (--skip-validation for repos with another convention): <type>(<scope>): <description>, e.g. fix(api): resolve race condition in request handler.
Body
| Shape | When | Sections |
|---|---|---|
| Task | We know what to do | What · Why · How |
| Open question | The fix is a decision | Question · What we found · Options |
| Bug | Behaviour differs from expected | What happens · Expected · How to reproduce |
- What: the change in product terms. What a user or caller can do afterwards.
- Why: the concrete problem, then the system explained so the reader gets it in
one read: terms defined once, what happens when, one real example link.
- How: "Guidance only." and 2–5 pointers (prior art, a link, a constraint that
rules out an obvious approach). Open points stay listed as open.
- Options: numbered, one line each with its cost, ending in "Something else?".
Cut implementation plans, edge-case lists, acceptance-criteria and testing-plan checklists, facts the reader can't check, and history. Prune each line: would the reader get the problem wrong without it? Then tighten with /pstack:unslop.
Script
scripts/gh_issue.py, run with uv run. Create and push show a preview and ask first; --yes skips it.
| Task | Command | ||
|---|---|---|---|
| Start a body | `init --template task\ | question\ | bug -o /tmp/issue.md` |
| Create | create owner/repo --title "…" --body-file /tmp/issue.md [--labels a,b] [--assignees @me] [--milestone M] [--project P] | ||
| Create a sub-issue | create-sub owner/repo --parent 10 --title "…" --body-file … | ||
| Link existing | link owner/repo --parent 10 --child 42 | ||
| Edit | edit owner/repo 123 [--title "…"] [--body-file …] | ||
| View / list | view owner/repo 123 · list owner/repo [--labels bug] | ||
| Sub-issues, incl. cross-repo | list-subissues owner/repo 123 [--json] | ||
| Comment / label / close | comment owner/repo 123 "…" · labels owner/repo 123 --add a,b · close owner/repo 123 --reason completed |
Round trip. dump-tree owner/repo 123 ./issues/ writes the issue and its sub-issues as markdown with YAML frontmatter (title, repo, number, labels, assignees, milestone, parent). Edit locally, then push ./issues/<file>.md: it updates the issue when number is set and creates one otherwise.
