OpenParable
Skip to content
← Back to skills

Gum Issue Creation

Productivity
gum-issue-creation

Gum Issue Creation is an Agent Skill for productivity published in the vchelaru/Gum repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

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).

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/vchelaru/Gum/blob/HEAD/.claude/skills/gum-issue-creation/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/gum-issue-creation, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Creating Gum Issues

Use gh issue create to file issues. Conventions:

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.

Multi-line bodies

gh runs through the Bash tool (bash, not PowerShell) — do NOT use PowerShell here-strings (@'...'@); a stray @ leaks onto the first body line. Write the body to a temp file and pass --body-file:

cat > /tmp/issue_body.md << 'EOF'
...body...
EOF
gh issue create --title "..." --body-file /tmp/issue_body.md --label bug
rm /tmp/issue_body.md

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.

Title

Specific and self-describing — names the feature area and the gap (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.