create-issue
Skill1 starsChanged 9 months agoMITView on GitHub
Create a GitHub issue following project conventions
67 other projects use a version of this.
Adopted by
Most recently taken up by
- torrust/torrust-trackertheir own version, first seen Nov 16, 2026
- TabbyML/pochitheir own version, first seen Nov 16, 2026
- antick/skillstheir own version, first seen Nov 16, 2026
- mlschodkowski/skillstheir own version, first seen Nov 16, 2026
- neko3cs/skillstheir own version, first seen Nov 8, 2026
- dsifry/metaswarmtheir own version, first seen Nov 8, 2026
Used with
Projects with it also use native-nostalgia-stack, software-engineering-excellence and 9 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
frostneySkillnative-nostalgia-stack
Applies the user's FreePascal toolchain and its build, formatting, hook, and test contracts while leaving project-specific mechanics local. Use when scaffolding or working in a FreePascal project that follows this toolchain.
Also in 3 projects that use this
frostneySkillsoftware-engineering-excellence
Applies the user's engineering standards during substantial technical work: preserve scope, use current evidence, delegate independent parts, and complete authorized outcomes. Use during substantial implementation, debugging, refactoring, or multi-part delivery work.
Also in 3 projects that use this
withpiperSkillroadmap-review
Audit roadmap health — issues, dependency order, spec coverage, doc freshness. Use when speccing a new initiative. Use when /phase-plan output looks suspicious. Use before /roadmap-create reruns.
Also in 3 projects that use this
GoogleSkillimplement-issue
Implement a Site Kit GitHub issue end-to-end from its implementation brief. Use when the user asks to implement, build, or work on a GitHub issue / feature by number (e.g. "implement issue #12345", "build the feature in issue 12345", "follow the implementation brief for #12345") in the google/site-kit-wp repo.
Also in 6 projects that use this
Microsoft AzureSkillcreate-release
Use when creating a new ASO release, including pre-checks, release notes generation, draft GitHub release creation, documentation updates, and ROADMAP changes.
Also in 4 projects that use this
MicrosoftSkillupdate-pr
Update the pull request for the current session. Use when the user wants to push new changes to an existing PR.
Also in 3 projects that use this
Other versions67 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 67
- penpot/penpot★ 62ksame name
- videojs/video.js★ 40ksame name
- yugabyte/yugabyte-db★ 11ksame name
- antiwork/gumroad★ 10ksame name
- gitkraken/vscode-gitlens★ 10ksame name
- camunda/camunda★ 4.4ksame name
- robustmq/robustmq★ 1.9ksame name
- aws-powertools/powertools-lambda-typescript★ 1.8ksame name
- classroomio/classroomio★ 1.7ksame name
- tikv/pd★ 1.2ksame name
57 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository10 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- clean-worktreesSkill
- commitSkill
- plan-issueSkill
- prSkill
- pushSkill
- review-codeSkill
- review-prSkill
- shipSkill
- start-issueSkill
The file
Files
Create Issue
Current State
- 기존 라벨: !
gh label list --limit 30 2>/dev/null || echo "라벨 목록을 가져올 수 없습니다"
Instructions
CLAUDE.md의 이슈 생성 규칙에 따라 GitHub 이슈를 생성한다.
1. 제목 결정
$ARGUMENTS가 있으면 제목으로 사용- 없으면 사용자에게 이슈 제목을 질문
- 검증: 한국어, 동사형으로 시작, 70자 이내
2. 우선순위 선택
AskUserQuestion으로 우선순위를 선택받는다:
{
"questions": [{
"question": "이슈의 우선순위를 선택해주세요.",
"header": "우선순위",
"options": [
{"label": "priority: high", "description": "우선 처리 필요"},
{"label": "priority: medium", "description": "일반 우선순위"},
{"label": "priority: low", "description": "여유 있을 때 처리"}
],
"multiSelect": false
}]
}3. 카테고리 선택
AskUserQuestion으로 카테고리를 선택받는다:
{
"questions": [{
"question": "이슈의 카테고리를 선택해주세요.",
"header": "카테고리",
"options": [
{"label": "enhancement", "description": "새 기능 또는 개선"},
{"label": "bug", "description": "버그 수정"},
{"label": "documentation", "description": "문서 작업"}
],
"multiSelect": false
}]
}4. 본문 작성
사용자에게 배경과 작업 내용을 질문한 뒤, 아래 형식으로 본문을 구성한다:
## 배경
{사용자 입력 또는 컨텍스트 기반 작성}
## 작업 내용
- [ ] 할 일 1
- [ ] 할 일 2
## 관련 파일
- `path/to/file`
## 비고
{추가 사항}5. 라벨 존재 확인
위에 주입된 기존 라벨 목록에서 사용할 라벨(status: ready, 선택된 우선순위, 선택된 카테고리)이 모두 존재하는지 확인한다.
- 존재하지 않는 라벨이 있으면
gh label create "<라벨명>" --color "<색상>"으로 생성한다status: ready→#0E8A16priority: high→#D93F0B,priority: medium→#FBCA04,priority: low→#C5DEF5enhancement→#A2EEEF,bug→#D73A4A,documentation→#0075CA
6. 이슈 생성
gh issue create \
--title "<제목>" \
--label "status: ready,priority: <선택>,<카테고리>" \
--body "<본문>"7. 결과 출력
생성된 이슈 URL을 반환한다.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

