메뉴
GitHub issue state machine and code integration patterns. Covers state transitions (needs-triage → accepted → in-progress → completed), branch naming (feat/123-desc), PR linking (Closes
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Validate documentation files for completeness, accuracy, and consistency with the codebase. Use when user mentions "check documentation", "validate docs", "is the README up to date?", requests documentation review, says "docs are wrong" or "fix the docs", or is working on documentation improvements. Covers README files, API docs, CHANGELOG, and any markdown documentation.
Git worktree patterns, best practices, templates, and quick reference. Use when user asks about "worktree best practices", "worktree patterns", "git worktree help", "worktree template", "worktree mode semantics", "what are worktree modes", "explain worktree metadata", or needs guidance on worktree organization and workflows.
Ansible automation reference for playbooks, roles, inventory, variables, and modules. Includes Proxmox VE and Docker integration via community.general and community.docker collections. Use when writing playbooks, troubleshooting Ansible runs, or designing automation workflows. Triggers: ansible, playbook, inventory, role, task, handler, vars, jinja2, galaxy, proxmox_kvm, proxmox_lxc, docker_container, docker_compose.
Docker and Docker Compose reference for container deployment, networking, volumes, and orchestration. Includes Proxmox hosting and LXC comparison patterns. Use when working with docker-compose.yaml, Dockerfiles, troubleshooting containers, or planning container architecture. Triggers: docker, compose, container, dockerfile, volume, network, service, lxc.
HashiCorp Packer reference for building machine images and VM templates. Use when working with Packer configurations (.pkr.hcl files), running packer commands, troubleshooting builds, or designing image pipelines. Includes Proxmox builder patterns for homelab environments. Triggers: packer, pkr.hcl, image, template, ami, builder, provisioner, cloud-init.
Proxmox VE virtualization platform reference for VM/LXC management, clustering, storage, and networking. Includes Terraform and Ansible integration patterns. Use when working with Proxmox configurations, CLI commands, troubleshooting VMs/containers, or planning resource allocation. Triggers: proxmox, qemu, kvm, lxc, pve, vm, container, cluster, vzdump, qm, pct.
| name | gh-issue-lifecycle |
| description | GitHub issue state machine and code integration patterns. Covers state transitions (needs-triage → accepted → in-progress → completed), branch naming (feat/123-desc), PR linking (Closes |
State machine for GitHub issues and how they connect to code.
┌─────────────────┐
│ needs-triage │ ← New issue created
└────────┬────────┘
│ triage
┌────────▼────────┐
┌───────────│ accepted │ ← In backlog
│ └────────┬────────┘
│ │ start work
│ ┌────────▼────────┐
│ ┌──────│ in-progress │ ← Active development
│ │ └────────┬────────┘
│ │ │ PR merged
│ │ ┌────────▼────────┐
│ │ │ completed │ ← Issue resolved
│ │ └─────────────────┘
│ │
│ │ blocked
│ │ ┌─────────────────┐
│ └─────►│ blocked │ ← Waiting on dependency
│ └─────────────────┘
│
│ needs-info
│ ┌─────────────────┐
└──────────►│ needs-info │ ← Waiting for clarification
└─────────────────┘
| State | Label | Meaning |
|---|---|---|
| New | needs-triage | Just created, not reviewed |
| Clarification | needs-info | Waiting on reporter |
| Backlog | accepted | Triaged, waiting for work |
| Active | in-progress | Someone is working on it |
| Blocked | blocked | Can't proceed |
| State | Reason | Comment |
|---|---|---|
| Completed | Fixed/implemented | Via PR or manual |
| Duplicate | Same as another | "Duplicate of #N" |
| Won't Fix | Out of scope | Explain why |
| Invalid | Not a real issue | Cannot reproduce |
| Stale | No activity | Auto-closed after warning |
When starting work on issue #123:
feat/123-short-description # feature
fix/123-short-description # bug fix
chore/123-short-description # maintenance
docs/123-short-description # documentation
i18n/locale-code # internationalization (e.g., i18n/zh-CN, i18n/ja-JP)
i18n/123-locale-code # i18n with issue (e.g., i18n/42-es-MX)
Examples:
feat/42-add-dark-modefix/123-login-timeoutchore/99-update-depsi18n/zh-CN - Chinese (Simplified) translationsi18n/42-ja-JP - Japanese translations for issue #42Include issue number in PR title:
feat: add dark mode (#42)
fix: resolve login timeout (#123)
chore: update dependencies (#99)
Use closing keywords in PR body:
| Keyword | Effect |
|---|---|
Closes #123 | Auto-closes when merged |
Fixes #123 | Same as Closes |
Resolves #123 | Same as Closes |
Example PR description:
## Summary
Add dark mode toggle to settings page.
Closes #42
## Changes
- Add theme context
- Create toggle component
- Update color variables
Reference issues without auto-close:
Related to #45
See also #67
Depends on #89
When closing without PR, always comment:
gh issue close 123 --comment "Duplicate of #456"
gh issue close 123 --comment "Closing as won't fix: [reason]"
gh issue close 123 --comment "Cannot reproduce with provided steps. Please reopen with more details if issue persists."
gh issue close 123 --comment "Closing due to inactivity. Please reopen if still relevant."
Issues with no activity for N days (typically 90):
# Find stale issues
gh issue list --search "updated:<$(date -v-90d +%Y-%m-%d)"
stale labelThis issue has been inactive for 90 days.
It will be closed in 30 days if there's no further activity.
Please comment if this is still relevant.
name: Stale Issues
on:
schedule:
- cron: '0 0 * * *'
jobs:
stale:
runs-on: ubuntu-latest
steps:
- uses: actions/stale@v9
with:
stale-issue-message: 'This issue has been inactive for 90 days.'
days-before-stale: 90
days-before-close: 30
stale-issue-label: 'stale'
# Close all issues with label
gh issue list --label "stale" --json number --jq '.[].number' | \
xargs -I {} gh issue close {} --comment "Closing stale issue"
# Add label to all issues matching query
gh issue list --search "is:open label:bug" --json number --jq '.[].number' | \
xargs -I {} gh issue edit {} --add-label "needs-review"
# Move issue to another repo
gh issue transfer 123 owner/other-repo
# Create branch from issue
gh issue develop 123 --checkout
# Or manually
git checkout -b fix/123-description main
gh issue edit 123 --add-label "in-progress"
# Create PR that closes issue
gh pr create --title "fix: resolve issue (#123)" --body "Closes #123"
gh issue edit 123 \
--remove-label "in-progress" \
--add-label "blocked"
gh issue comment 123 --body "Blocked on #456"
Closes #123This skill defines how issues move through states:
needs-triage → Initial state (set by gh-issue-templates)accepted → After triage (applied by gh-wrangler using gh-issue-triage)in-progress → Work started (manual or via branch creation)blocked → Can't proceed (set manually with comment)When starting work on an issue:
# Branch naming from this skill
git checkout -b feat/123-description
# PR creation with linking
gh pr create --title "feat: description (#123)" --body "Closes #123"
gh-issue-templates - Creating well-formatted issuesgh-issue-triage - Labeling and prioritizationgh-wrangler - Interactive lifecycle management