メニュー
Draft and create a focused GitHub issue for World of ClaudeCraft using the project issue format. Use only when the user explicitly asks to file, create, or open an issue. A request for a draft does not authorize creating the issue.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Audit World of ClaudeCraft Codex support for current conventions, model neutrality, instruction quality, agent safety, skill design, hooks, CI integration, and documentation drift. Use when reviewing or modernizing AGENTS.md, .codex, .agents, Codex workflows, Codex-facing scripts, or the repository AI architecture.
Implement World of ClaudeCraft features, bug fixes, and focused refactors using module-first design and behavior-driven tests. Use when adding behavior, fixing a defect, extracting logic from a large file, or moving code behind an existing architectural seam.
Plan a large or multi-session World of ClaudeCraft feature as architecture-aligned vertical slices with explicit decisions, verification, and handoff state. Use when the user requests a phased implementation plan, planning packet, session breakdown, or scalable approach before implementation.
Run end-of-contribution QA for World of ClaudeCraft, including readiness checks, scoped regression testing, and conditional specialist review. Use when asked to QA changes, make work ready, verify a branch or worktree, or assess whether a contribution is complete.
Perform a whole-tree World of ClaudeCraft release malware audit using the deterministic scanner plus contextual triage. Use before a release, for a release tag or branch, after suspicious dependency or install changes, or when explicitly asked for a malware-focused security review.
Audit a release merge into a long-lived World of ClaudeCraft branch for semantic conflict damage, legacy drift, missed inventory updates, and invalidated planning assumptions. Use after merging a release branch, when reviewing a release merge commit, or before resuming feature work after upstream integration.
| name | woc-file-issue |
| description | Draft and create a focused GitHub issue for World of ClaudeCraft using the project issue format. Use only when the user explicitly asks to file, create, or open an issue. A request for a draft does not authorize creating the issue. |
Create a clear, bounded issue in levy-street/world-of-claudecraft.
Write to GitHub only when the user explicitly asks to file, create, or open the issue. For draft, rewrite, or proposal requests, return text only. Do not add labels, milestones, projects, or assignees unless requested or unambiguously specified.
CLAUDE.md files.Do not invent reproduction results, environment details, ownership, severity, or implementation decisions.
Use a concise title with the affected area. Structure the body around the problem or opportunity, current and expected behavior, scope, acceptance criteria, relevant implementation context, and verification expectations.
For a bug, include reproduction steps, actual and expected results, and environment only when known. Use unchecked tasks only for independently verifiable acceptance criteria. Put unknown details in HTML comments instead of presenting guesses as facts.
Create with gh issue create only after the authorization condition is satisfied.
Return the final title, issue URL if created, assumptions, and confirmation that no extra
metadata changed unless requested.