메뉴
Standardized GitHub issue templates for bugs, features, and tasks. Provides title formats, body structure, and required sections. Use when creating issues to ensure consistency. Includes copy-paste templates in templates/ directory.
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-templates |
| description | Standardized GitHub issue templates for bugs, features, and tasks. Provides title formats, body structure, and required sections. Use when creating issues to ensure consistency. Includes copy-paste templates in templates/ directory. |
Standardized formats for creating GitHub issues with consistent structure.
| Type | Title Prefix | Key Sections |
|---|---|---|
| Bug | bug: | Describe, Expected, Steps, Environment |
| Feature | feat: | Problem, Solution, Alternatives, Acceptance |
| Task | task: or chore: | Description, Checklist, Context |
Title: bug: <short description>
Body:
## Describe the bug
<!-- What happened? -->
## Expected behavior
<!-- What should have happened? -->
## Steps to reproduce
1.
2.
3.
## Environment
- OS:
- Version:
- Relevant config:
## Logs/Screenshots
<!-- If applicable -->
Good:
bug: login fails with expired OAuth tokenbug: dashboard crashes when filter is emptyBad:
bug: it's brokenbug: doesn't workTitle: feat: <short description>
Body:
## Problem
<!-- What problem does this solve? -->
## Proposed solution
<!-- How should it work? -->
## Alternatives considered
<!-- Other approaches you thought of -->
## Acceptance criteria
<!-- How do we know it's done? -->
- [ ] Criterion 1
- [ ] Criterion 2
Good:
feat: add CSV export for reportsfeat: support dark mode in settingsBad:
feat: make it betterfeat: new featureTitle: task: <short description> or chore: <short description>
Use task: for project work, chore: for maintenance/deps/infra.
Body:
## Description
<!-- What needs to be done? -->
## Checklist
- [ ] Step 1
- [ ] Step 2
- [ ] Step 3
## Context
<!-- Why is this needed? -->
Good:
task: set up CI pipelinechore: upgrade React to v19chore: update dependenciesBad:
task: do the thingchore: stuffIs something broken?
YES → Bug Report
NO → Continue
Is this new functionality?
YES → Feature Request
NO → Continue
Is this maintenance/infrastructure?
YES → Task (chore:)
NO → Task (task:)
See templates/ for copy-paste ready files:
bug.md - Bug report templatefeature.md - Feature request templatetask.md - Task/chore templateAfter using this skill to create an issue, use:
gh issue creategh-issue-triage - Labeling and prioritization rulesgh-issue-lifecycle - State transitions and linkinggh-wrangler - Interactive issue management