메뉴
Create well-structured GitHub issues following the Epic > Feature > Task/Bug hierarchy. Uses GitHub issue types (not labels) and relationships to connect related issues. Invoke with /github-issue.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
SOC 직업 분류 기준
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/divinevideo/divine-mobile --skill github-issue명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
SKILL.md 표시 중
Run and debug Flutter E2E integration tests that exercise the real app against a local Docker backend (no mocks). Use when running E2E tests, debugging failures, or working on the local harness.
Fix ArgoCD ExternalSecret deployment failing with "namespace X is not permitted in project Y". Use when: (1) ExternalSecret shows OutOfSync in ArgoCD but won't sync, (2) ArgoCD application status shows "namespace X is not permitted in project 'infrastructure'", (3) ExternalSecret targets a namespace managed by a different ArgoCD project, (4) Using apps-of-apps pattern with separate infrastructure and application projects.
Art direction for any content — reads text, PDF, Word, HTML, PPT, then proposes 2-3 creative directions with photography style, mood, and visual language. After selection, generates AI image prompts and visual briefs section-by-section. Use when the user shares content and needs visual direction, image sourcing, or creative direction for any material.
| name | github-issue |
| description | Create well-structured GitHub issues following the Epic > Feature > Task/Bug hierarchy. Uses GitHub issue types (not labels) and relationships to connect related issues. Invoke with /github-issue. |
| author | Claude Code |
| version | 1.1.0 |
| date | "2026-02-09T00:00:00.000Z" |
| user_invocable | true |
| invocation_hint | /github-issue |
| arguments | Required: Description of the issue to create Example: /github-issue profile stats text wrapping bug Example: /github-issue add video download feature If no argument is provided, ask the user what issue they want to create. |
Help create well-structured GitHub issues that follow the project's hierarchy,
conventions, and existing templates from .github/ISSUE_TEMPLATE/.
Epic (large initiative, multiple features)
└── Feature (user-facing capability, multiple tasks)
└── Task (single unit of work)
└── Bug (defect to fix)
| Type | Title Prefix | Use When |
|---|---|---|
| Epic | epic: | Large initiative spanning weeks/months |
| Feature | feat: | New user-facing capability |
| Task | task: | Single unit of implementation work |
| Bug | fix: | Something is broken/not working as expected |
.github/ISSUE_TEMPLATE/bug_report.yaml)Title format: fix: <description>
## Summary
[One sentence about what's broken]
## Environment
- App version: [e.g., 1.2.3]
- Device: [e.g., iPhone 14 Pro, iOS 17.1]
- Network: [WiFi / Cellular]
## Steps to Reproduce
1. Go to '...'
2. Click on '...'
3. See error
## Actual Result
[What actually happened]
## Expected Result
[What you expected to happen]
## Regression?
[Yes / No / Unknown - Did this work in a previous version?]
## Evidence
[Screenshots, screen recordings, logs, crash reports]
.github/ISSUE_TEMPLATE/feature_request.yaml)Title format: feat: <description>
[Describe the feature or improvement]
[What problem does this solve or what does it make easier?]
[Describe a situation where you'd need this feature]
[Screenshots, mockups, examples from other apps]
Title format: task: <description>
## Description
[Clear description of what needs to be done]
## Context
[Why this task is needed]
## Implementation Notes
[Technical approach, files to modify, considerations]
## Acceptance Criteria
- [ ] Criterion 1
- [ ] Criterion 2
## Testing
[How to verify this task is complete]
Title format: epic: <description>
## Overview
[High-level description of the initiative]
## Goals
- [ ] Goal 1
- [ ] Goal 2
## Features
- [ ] #XXX Feature name
- [ ] #YYY Feature name
## Success Criteria
[How we know this epic is complete]
## Notes
[Additional context, constraints, or considerations]
Use GitHub's sub-issue API (NOT text like "Part of #123" in the body):
| Relationship | How |
|---|---|
| Parent/Child | addSubIssue GraphQL mutation |
| Related | Related to #789 in body text |
| Blocks | Blocks #101 in body text |
| Blocked by | Blocked by #102 in body text |
.github/ISSUE_TEMPLATE/gh issue create \
--title "fix:|feat:|task:|epic: Description" \
--body "..." \
--assignee NotThatKindOfDrLiz
Available types and their IDs (repo: divinevideo/divine-mobile):
IT_kwDODpf9Q84ByDODIT_kwDODpf9Q84ByDOEIT_kwDODpf9Q84ByDOF# Get the issue node ID
gh api graphql -f query='{ repository(owner: "divinevideo", name: "divine-mobile") {
issue(number: ISSUE_NUMBER) { id }
} }'
# Set the type
gh api graphql -f query='mutation { updateIssueIssueType(input: {
issueId: "ISSUE_NODE_ID",
issueTypeId: "TYPE_ID"
}) { issue { id } } }'
# Get parent issue node ID
gh api graphql -f query='{ repository(owner: "divinevideo", name: "divine-mobile") {
issue(number: PARENT_NUMBER) { id }
} }'
# Add as sub-issue
gh api graphql -f query='mutation { addSubIssue(input: {
issueId: "PARENT_NODE_ID",
subIssueId: "CHILD_NODE_ID"
}) { issue { id } subIssue { id } } }'
Before creating a Task or Bug, search for related Features/Epics:
gh issue list --search "related keywords" --limit 10
Use correct title prefix: fix:, feat:, task:, epic:
One issue, one concern: Don't combine multiple bugs or features
Use sub-issue API for hierarchy: Never use "Part of #XXX" text, use GraphQL addSubIssue
Include context: Explain why, not just what
Be specific: Include file paths, error messages, steps to reproduce
Match existing templates: Follow the structure from .github/ISSUE_TEMPLATE/
gh issue create \
--title "fix: Profile stats labels wrap incorrectly on small screens" \
--body "$(cat <<'EOF'
## Summary
Profile stats labels ("Followers", "Following") wrap to multiple lines, splitting words mid-word.
## Environment
- App version: Latest
- Device: Small screen devices
- Network: N/A
## Steps to Reproduce
1. Open profile screen on a small device or narrow width
2. Look at the stats row (Videos, Followers, Following)
3. See labels wrapping incorrectly
## Actual Result
Labels wrap mid-word:
- "Followers" becomes "Follower" + "s"
- "Following" becomes "Followin" + "g"
## Expected Result
Labels should remain on a single line, or truncate with ellipsis if needed.
## Regression?
Unknown
## Evidence
<!-- Screenshot to be attached after creation -->
EOF
)"