agentleFS
vchelaruvchelaru/Gum/.claude/skills/gum-issue-creation/SKILL.md

gum-issue-creation

Skill659 starsChanged 2 months agoMITView on GitHub

Conventions for filing GitHub issues in the Gum repo via gh. Triggers when the user asks to "log an issue", "create an issue", "file a bug", or otherwise capture a problem/idea as a GitHub issue (as opposed to fixing one).

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 3 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use gh issue create to file issues.

    line 8
  2. Distinctive:

    Suggested improvement: must not assert an unverified convention ("editors conventionally do X").

    line 21
  3. Very specific:

    Use a real multi-line value for issue comments, issue bodies, and PR bodies.

    line 29
  4. Very specific:

    After creating or editing a multi-line body, read it back before reporting success.

    line 46
  5. Distinctive:

    Keep it scannable for a future implementer:

    line 49
  6. Distinctive:

    After creating, report the issue URL back to the user.

    line 58

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Creating Gum Issues

Use gh issue create to file issues. Conventions:

Before researching the source pointer

Check the skills list for one matching the feature area and load it before grepping for the file:line pointer — CLAUDE.md's "load matching skills before investigating" rule applies to issue research too, not just edits. A matching skill (e.g. gum-tool-variable-grid for a Variables-tab/displayer report) names the relevant files and known gotchas directly instead of rediscovering them by grep.

Don't file

SokolGum and Maui are not maintained. Don't edit them, don't mention them in reports, PR bodies or briefs, don't file or work on issues that exist only for them, and a feature that ships on the MonoGame family, raylib, and Skia but not SokolGum is not a tracked gap.

FlatRedBall 1 (FRB1) is frozen. It changes only when a game that uses it needs a change, so don't file issues about behavior that is wrong only in the FRB1 build, and don't fix or pin it unprompted. Shared source still has to compile for FRB1 (the FRB canary), and #if FRB code is left alone.

Issues you file yourself

A value you printed while diagnosing something else is an observation, not a report — name what a user would see, or don't file. Say in the body that it came from instrumentation.

Suggested improvement must not assert an unverified convention ("editors conventionally do X"). Verify it or write it as an open question: asserted, it becomes the issue's premise, and whoever picks the issue up implements against it without rechecking.

Labels

  • Bug reports get --label bug (label exists, color #fc2929). Apply it at creation time.
  • The bug label is real and applies silently — don't second-guess it or omit it on later issues.
  • An issue that needs Vic's decision gets --label "needs discussion" at creation (behavior changes that could move existing projects, open design questions). Vic finds his decision queue by this label.

Multi-line GitHub bodies

Use a real multi-line value for issue comments, issue bodies, and PR bodies. Never write literal \n sequences and expect GitHub Markdown to turn them into line breaks.

Match the syntax to the active shell. In PowerShell, use a here-string:

$githubBody = @'
...body...
'@
gh issue create --title "..." --body $githubBody --label bug

In Bash, use a heredoc or --body-file:

gh issue create --title "..." --body-file /tmp/issue_body.md --label bug

After creating or editing a multi-line body, read it back before reporting success. Use gh issue view <number> --json body for issues and gh pr view <number> --json body for PRs.

Body structure

Keep it scannable for a future implementer:

  • Problem — what's wrong / the user's report, verbatim intent preserved.
  • Suggested improvement (when applicable) — concrete target behavior or message.
  • Source — file:line pointer(s) found by a quick Grep, plus a one-line note on what the fix touches. A precise pointer turns a vague report into actionable work; spend a moment to find it.
  • Reach — how a user lands on the broken code path, and whether that path is the recommended route or a legacy corner the tool never produces on its own. A defect reachable only through hand-authored input is near-zero impact; say so instead of letting it read like an ordinary bug.

Title

Specific and self-describing, phrased as what should be true (X should Y) rather than a description of the current problem, e.g. Animation keyframe "Could not find state or animation" error should name the missing reference, not a generic summary.

After creating, report the issue URL back to the user.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.