Skip to content
Skills Library
Programming · Writing

file-issue

/file-issue

Create a GitHub issue for World of ClaudeCraft in the maintainer's house format. Use when asked to file, open, or create a GitHub issue or bug report from a description, a screenshot, or a rough placeholder. Rewrites the input into a clean, professional issue (Problem, Steps to reproduce, Expected, Actual, Scope, Acceptance criteria) and includes a Screenshot section only for UI/UX issues. Posts to rowdybard/whetstorm via gh.

Licence
MIT
Last repository change
25.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
1
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 25.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What to check before installing
  • SKILL.md zawiera komentarze HTML (1). Nie widać ich w podglądzie Markdown, a model je czyta.

What it does and when to use it

Create a GitHub issue for World of ClaudeCraft in the maintainer's house format. Use when asked to file, open, or create a GitHub issue or bug report from a description, a screenshot, or a rough placeholder. Rewrites the input into a clean, professional issue (Problem, Steps to reproduce, Expected, Actual, Scope, Acceptance criteria) and includes a Screenshot section only for UI/UX issues. Posts to rowdybard/whetstorm via gh.

Original author description

Create a GitHub issue for World of ClaudeCraft in the maintainer's house format. Use when asked to file, open, or create a GitHub issue or bug report from a description, a screenshot, or a rough placeholder. Rewrites the input into a clean, professional issue (Problem, Steps to reproduce, Expected, Actual, Scope, Acceptance criteria) and includes a Screenshot section only for UI/UX issues. Posts to rowdybard/whetstorm via gh.

How it works

  1. Voice and rules
  2. Step 1: Gather and classify
  3. Step 2: Draft the body
  4. Step 3: Screenshot section (UI/UX issues only)
  5. Step 4: Create it
Original SKILL.md headings · 125 lines, 751 words
SKILL.md preview
---
name: file-issue
description: Create a GitHub issue for World of ClaudeCraft in the maintainer's house format. Use when asked to file, open, or create a GitHub issue or bug report from a description, a screenshot, or a rough placeholder. Rewrites the input into a clean, professional issue (Problem, Steps to reproduce, Expected, Actual, Scope, Acceptance criteria) and includes a Screenshot section only for UI/UX issues. Posts to rowdybard/whetstorm via gh.
user-invocable: true
---

> **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 an issue (World of ClaudeCraft house style)

Turn a rough description, screenshot, or placeholder into a clean, professional GitHub
issue that matches how the maintainer writes them, then create it on the canonical repo.
Reference issues for the voice and shape: `#1050` (feature/behavior) and `#1051`
(UI/UX bug with a screenshot section).

## Voice and rules

- Plain, professional, calm. No marketing, no preamble, no AI voice.
- **No em dashes, en dashes, or emojis** anywhere in the title or body. Use commas,
  colons, parentheses, or "to" for ranges. (This repo bans them; do not introduce them.)
- Be specific and factual. Rewrite vague placeholder copy into concrete, testable
  statements. If a detail is unknown, leave a clearly marked HTML comment rather than
  guessing a fact.
- Title: short and descriptive, stating the problem (for example, "Unable to scroll the
  world market UI on mobile"). A severity prefix ("Critical: ...") is optional and only
  for genuinely high-severity issues, matching the maintainer's style in `#1050`.

## Step 1: Gather and classify

From the user's input work out:

- The core problem in one or two sentences.
- Whether it is a **bug** (something is broken) or a **request** (new or changed
  behavior). Bugs get Steps to reproduce plus Actual behavior; requests usually do not.
- Whether it is **UI/UX related** (visual, layout, HUD, mobile, input, rendering). Only
  UI/UX issues get the Screenshot section.
- Whether it is **platform or device specific** (mobile, landscape, a browser). If so,
  include an Environment section.

If the core problem or the expected behavior is genuinely unclear, ask one short
clarifying question before drafting. Do not stall on details you can reasonably infer
from a screenshot or the description, note inferred specifics back to the user instead.

## Step 2: Draft the body

Use this section set. Include the core sections always; include the situational ones
only when they apply. Keep each section tight.

Core (always):

```
## Problem

<One to three short paragraphs: what is wrong or missing, and why it matters.>

## Expected behavior

- <Bulleted, concrete, observable statements of what should happen.>

## Scope

<What to investigate or change. A short bulleted list of the affected areas/tabs/flows.>

## Acceptance criteria

- <Checkable conditions that mean this is done. Mirror the Expected behavior, made testable.>
- <For UI/mobile bugs, include "the desktop experience is unchanged" or the equivalent.>
```

Situational (include only when they apply):

```
## Steps to reproduce        # bugs only

1. <step>
2. <step>
3. <observe the failure>

## Actual behavior           # bugs only

- <What actually happens today, the mirror of Expected behavior.>

## Environment               # platform/device-specific only

- Platform: <mobile web landscape / desktop / etc.>
- Surface: <in-game HUD window, guide page, admin, etc.>

## Notes                     # optional: likely root cause, non-goals, related work
```

## Step 3: Screenshot section (UI/UX issues only)

If, and only if, the issue is UI/UX related, append a Screenshot section as a placeholder
the user fills in later. If the user already provided an image, still leave the
placeholder (issues are created from text via `gh`; the user attaches the image in the
GitHub web UI afterward) and tell them where to drop it.

```
## Screenshot

<!-- Only add a screenshot if this issue is UI/UX related. Drag the image in here. -->
```

For a non-UI issue (logic, server, balance, content), omit the Screenshot section
entirely.

## Step 4: Create it

Write the body to a temp file and create the issue on the canonical repo. Always
`rowdybard/whetstorm`, never a fork.

```
gh issue create \
  --repo rowdybard/whetstorm \
  --title "<title>" \
  --body-file <path-to-body.md>
```

Use `--body-file` (not `--body`) so headings, lists, and the HTML comment survive shell
quoting. Add `--label`/`--assignee` only if the user asked for them.

Creating an issue is outward-facing, but invoking this skill IS the request to create it,
so create directly. Then report back: the issue URL, the title, and a one-line note of
any specifics you inferred (so the user can correct them) plus, for UI/UX issues, a
reminder that the Screenshot section is waiting for their image.

Versions

RepositoryScoreLicence
This page · rowdybard/whetstorm-art100MIT
sma1lboy/rove100MIT
callstackincubator/cordierite95MIT
Er2oneousbit/claude-code-game-kit86MIT

Database snapshot: 13.11.2026 · package version ce0039949dd6 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100create-github-issue
    Create GitHub issues using the gh CLI. Use when the user wants to create a new issue, report a bug, request a feature, or create a task in GitHub. Trigger keywords - create issue, new issue, file bug, report bug, feature request, github issue.
  • 90woc-file-issue
    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.
  • 100create-issue
    Use when asked to file, report, open, or raise a GitHub issue for a bug, feature, audit, or review finding.
  • 100gh-create-issue
    Use when asked to file, report, open, or raise a GitHub issue for a bug, feature, audit, or review finding.
  • 100issue-writer
    Turn a rough bug report, idea, or complaint into an actionable issue by investigating the codebase first for reproduction steps, expected vs actual behaviour, suspected location, and acceptance criteria, then filing it with gh or emitting paste-ready markdown. Use when asked to…
  • 100review-pr
    Review a GitHub pull request for World of ClaudeCraft the way the maintainer does. Use when asked to review a PR, look at a PR, or check a PR (a github.com/.../pull/<n> link or a PR number). Fetches the PR, classifies the change by domain (sim, wire/parity, render, ui, server,…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.