メニュー
GitHub issue creation best practices including label verification, format standards, and systemic issue detection. Prevents duplicate work and ensures proper categorization.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/elevanaltd/eav-cep-assist --skill github-issue-creationコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
SOC 職業分類に基づく
| name | github-issue-creation |
| description | GitHub issue creation best practices including label verification, format standards, and systemic issue detection. Prevents duplicate work and ensures proper categorization. |
| allowed-tools | Read, Bash |
ISSUE_MASTERY::[LABEL_VERIFICATION+FORMAT_STANDARDS+SYSTEMIC_DETECTION]→CLEAR_BACKLOG
BEFORE_CREATE::[
MANDATORY::check_existing_labels[gh_label_list_OR_GitHub_UI],
COMMAND::"gh label list",
VERIFY::label_exists_before_applying[prevents_typos+maintains_taxonomy],
COMMON_LABELS::[bug, enhancement, documentation, technical-debt, security, performance]
]
LABEL_SELECTION::[
SINGLE_TYPE::choose_one[bug|enhancement|chore],
OPTIONAL_MODIFIERS::[priority-high, needs-investigation, cross-app],
ANTI_PATTERN::NEVER[create_new_labels_without_discussion, apply_nonexistent_labels]
]
TITLE::[
PATTERN::"[Component] Brief description",
EXAMPLES::["[Auth] RLS policy blocks valid users", "[CI] Flaky test in scenes-web", "[Docs] Missing API examples"],
RULES::[descriptive≠vague, component_prefix_when_relevant, <80_chars]
]
BODY_STRUCTURE::[
CONTEXT::"What's happening? Why is this important?",
EXPECTED::"What should happen instead?",
CURRENT::"What actually happens?",
REPRODUCTION::"Steps to reproduce (if bug)",
OPTIONAL::[screenshots, logs, related_issues]
]
TEMPLATE_EXAMPLE::
"""
**Context:**
Users with valid session tokens are getting 403 errors when accessing script comments.
**Expected:**
Authenticated users should be able to read comments on their own scripts.
**Current:**
403 Forbidden error from Supabase RLS policy.
**Reproduction:**
1. Login as test user
2. Navigate to script with comments
3. Observe error in console
"""
CREATE_ISSUE_WHEN::[
SYSTEMIC::cannot_fix_immediately[requires_prioritization],
CROSS_APP::coordination_required[multiple_apps_affected],
TECHNICAL_DEBT::refactoring_needed[paydown_strategy],
DISCOVERED_BUGS::deprioritized[fix_later],
SECURITY_PERFORMANCE::investigation_required[deep_analysis],
RECURRING::pattern_observed[happens_across_apps]
]
SKIP_ISSUE_WHEN::[
IMMEDIATE_FIX::resolved_current_session[just_fix_it],
MINOR_DETAIL::solved_during_feature[no_tracking_needed],
TEMPORARY::scaffolding[documented_in_.coord],
ALREADY_TRACKED::[TodoWrite_sufficient, PROJECT_CHECKLIST_covers]
]
COORDINATION_PHILOSOPHY::[
GIT_ISSUES::long_term_backlog+prioritization+cross_session_visibility,
COORD_DOCS::binding_decisions+system_state+phase_artifacts,
TODOWRITE::current_session_task_execution
]
STEP_BY_STEP::[
1→verify_labels::"gh label list"→choose_existing,
2→check_duplicates::"gh issue list --search 'keyword'"→avoid_redundancy,
3→draft_title::"[Component] Clear description",
4→write_body::context→expected→current→reproduction,
5→apply_labels::verified_labels_only,
6→create::"gh issue create --title '...' --body '...' --label '...'"
]
COMMAND_EXAMPLES::[
list_labels::"gh label list",
search_existing::"gh issue list --search 'RLS policy'",
create_issue::"gh issue create --title '[Auth] RLS circular dependency' --body '$(cat issue.md)' --label 'bug,priority-high'",
interactive::"gh issue create" # Opens editor for body
]
AVOID::[
SKIP_LABEL_CHECK::applying_nonexistent_labels→orphaned_issues,
VAGUE_TITLES::"fix stuff"→unsearchable,
NO_CONTEXT::"doesn't work"→cannot_reproduce,
PREMATURE_ISSUES::tracking_trivial_tasks→noise,
DUPLICATE_TRACKING::issue+TodoWrite+PROJECT_CHECKLIST→confusion
]
QUALITY_GATE::[
BEFORE_CREATE::ask["Is this systemic?", "Can I fix it now?", "Do labels exist?"],
LABEL_VERIFIED::command_run_confirms_label_exists,
FORMAT_FOLLOWED::title_pattern+body_structure,
NO_DUPLICATES::search_performed_first
]
CONSULTED_BY::[implementation-lead, holistic-orchestrator, quality-observer, principal-engineer]
TRIGGERS::[
SYSTEMIC_ISSUE_DETECTED,
CROSS_APP_CONCERN_IDENTIFIED,
TECHNICAL_DEBT_DISCOVERED,
RECURRING_PATTERN_OBSERVED
]
AUTHORITY::ADVISORY[suggest_issue_creation_when_appropriate≠force]
CORE_TRUTH::"Labels organize, format clarifies, systemic detection prevents noise"
REMEMBER::[
"Always verify labels exist before creating issue",
"Fix immediately if possible → Skip issue creation",
"Context+Expected+Current = Actionable issue",
"Search before creating → Prevent duplicates",
"Systemic issues deserve tracking → Trivial tasks don't"
]
HO lane discipline enforcement. Coordination-only tools. Prevents direct code implementation, enforces delegation to specialists. Auto-loads on /role ho activation. CRITICAL for preventing orchestrator drift into implementation.
Document placement rules, visibility protocols, and timeline test (before-code vs after-code). Defines where documentation belongs (dev/docs/ vs coordination/), documentation-first PR protocol, and phase artifact placement. Critical for documentation organization and visibility.
Intelligent POC-to-production code extraction with architectural awareness. Analyzes dependencies, adapts patterns, makes extraction strategy decisions (copy/adapt/rewrite), maintains system coherence. Performs pre-extraction analysis, transformation reasoning, quality gate enforcement, evidence-based commits. Use when extracting code requires understanding architecture, adapting patterns, threading parameters, or maintaining coherence across modules. Triggers on understand and extract, analyze dependencies, adapt pattern, extraction strategy, architectural extraction, intelligent migration.