메뉴
Use when asked to create or draft GitHub issues. Do not use when asked only to "plan" issues.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | github-issues-draft |
| description | Use when asked to create or draft GitHub issues. Do not use when asked only to "plan" issues. |
Use this skill when the user wants issue drafts prepared for review before publishing.
date -u +"%Y-%m-%dT%H-%M-%SZ" and write draft TOML to docs/issues/<timestamp>.toml using [[issues]] entries.docs/issues/.gitignore:
docs/issues is newly created in this task: create docs/issues/.gitignore containing *docs/issues/.gitignore is missing: create it and add an entry to ignore the generated draft filenameSKILL.md):
python3 scripts/publish_issues.py --validate <draft-path>python3 /absolute/path/to/skills/github-issues-draft/scripts/publish_issues.py <draft-path>).title is required and should be concise.body is Markdown, should be concise while still including enough detail to act on, and should be written as a TOML multiline string ("""...""").### headings.Top-level keys:
[defaults] (optional; use only when creating multiple issues)[[issues]] (required, non-empty)[defaults] allowed keys:
repo (string)assignees (array of strings)labels (array of strings)milestone (string)project (string or array of strings)template (string)[[issues]] allowed keys:
title (required, non-empty string)body (string)body_file (string)Rules:
body and body_file are mutually exclusive after defaults+issue merge.[defaults] only when drafting multiple issues; when used, prefer it for shared/common fields.repo.Script path (relative to this SKILL.md):
scripts/publish_issues.pyModes:
python3 scripts/publish_issues.py --validate <file> (alias: --dry-run)python3 scripts/publish_issues.py <file>Publish behavior:
gh outputcreated X, failed YWrite plans intended for a cheaper or less capable implementation model. Use when the user asks for a plan suitable for another LLM, junior engineer, intern, cheaper model, coding agent, or implementation delegate.
Use when the user asks for ideas, brainstorming, discussion, exploration, possibilities, pros and cons, tradeoffs, or to "think through" something.
Use this skill when asked to plan something, or plan and implement. Do not use when asked to implement a plan.
Use when initializing Rust projects or modifying Cargo.toml, Cargo.lock, cargo config, or other cargo-related files. Prefer this skill for dependency changes, features, package metadata, workspaces, and cargo commands. Do not load it for editing Rust source code generally.
Split an existing commit or PR into smaller reviewable pieces through a one-hunk patch queue. Use when extracting part of a commit, splitting a commit into multiple commits, or splitting PR changes from one or more source commits without starting from direct source edits.
Checkpoint, inspect, and return through session tree branches. Use when exploring uncertain approaches, investigating code, or when the user asks for a forked agent.