Skip to content

rowdybard/whetstorm-art / .agents/skills/woc-file-issue

woc-file-issue

Verified

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.

Whetstorm fork guard (read first). This skill was written for the upstream project. Never run gh against rowdybard/whetstorm: the CLI on this machine is signed in to the Whetstorm owner's account, so anything posted there goes out under their name. This fork's own repo is rowdybard/whetstorm: target it instead, and check that every gh command names it explicitly with --repo rowdybard/whetstorm.

File GitHub Issue

Create a clear, bounded issue in rowdybard/whetstorm.

Confirm authorization

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.

Research

  1. Read the root and relevant local CLAUDE.md files.
  2. Inspect enough current code or documentation to avoid stale assumptions.
  3. Search open issues when duplicate risk is meaningful.
  4. Ask one blocking question only when expected behavior or scope cannot be inferred.

Do not invent reproduction results, environment details, ownership, severity, or implementation decisions.

Write

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.

receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall