Creates well-structured GitHub issues for the Gum repository using the gh CLI.
npx skills add https://github.com/vchelaru/Gum --skill gum-issue-creation
Please help me install this Agent Skill. Skill: gum-issue-creation Source: https://github.com/vchelaru/Gum/tree/main/.claude/skills/gum-issue-creation Command: npx skills add https://github.com/vchelaru/Gum --skill gum-issue-creation
Filing GitHub issues that are vague, mislabeled, or poorly formatted wastes maintainer time and delays fixes. This Skill enforces the Gum repository's conventions so every issue you file is specific, labeled correctly, and actionable for whoever picks it up.
gh issue create with the correct bug label applied at creation time, plus rules for when not to file (e.g., Sokol feature-parity gaps are not tracked).--body-file patterns so GitHub Markdown renders real line breaks instead of literal \n sequences.Ask the assistant to log a GitHub issue in the Gum repo describing the problem you just observed, including where in the source it occurs.
High-intent search queries and answers about installing and using this skill.
Use gh issue create with a title, body, and labels. For multi-line bodies, use a PowerShell here-string or a Bash heredoc or --body-file so GitHub renders real line breaks instead of literal \n sequences.
Structure the body with a Problem section describing what is wrong, a Source section with file:line pointers found by grepping, and a Reach section explaining how users hit the broken path. Add a Suggested improvement section when a concrete target behavior exists.
Literal \n sequences appear when the shell string is not a real multi-line value, since GitHub Markdown does not convert them into line breaks. Use a PowerShell here-string, a Bash heredoc, or gh's --body-file flag, then verify with gh issue view --json body.
Do not file issues for Sokol feature-parity gaps, since SokolGum is not held to per-backend parity with MonoGame, raylib, or Skia. Also avoid filing raw diagnostic observations that no user would ever see.
Pass --label bug to gh issue create at creation time so the label applies immediately. In the Gum repo the bug label exists and should be applied to all bug reports without second-guessing.
rioX432Investigate codebase issues in a forked context and produce a report with file:line references.
Hack23Automate GitHub issue triage with labels, priorities, and assignments.
ShopifyClassify GitHub issue priority, detect duplicates, and apply labels via gh CLI.
gittowerResolve small local maintenance tasks with test-first implementation and Codex review.