quick-issue

Optional flags (in $ARGUMENTS):

• --label <name> - Add a label (can be used multiple times)
• --no-branch - Create issue only, skip branch creation
• --type <fix|feat|chore> - Set work type (default: fix)
  • fix → adds bug label, creates fix/ branch
  • feat → adds enhancement label, creates feat/ branch
  • chore → no automatic label, creates chore/ branch

Optional environment variables:

• GHPM_PROJECT - GitHub Project number to add issue to (e.g., export GHPM_PROJECT=7)

<usage_examples> Bug fix (default):

/ghpm:quick-issue Fix the login redirect loop when session expires

Output:

✓ Issue #42 created: "Fix the login redirect loop when session expires"
  https://github.com/owner/repo/issues/42
  Labels: bug
✓ Branch created: fix/issue-42-login-redirect-loop
✓ Switched to branch fix/issue-42-login-redirect-loop

Ready to work on issue #42. What would you like me to do first?

New feature:

/ghpm:quick-issue Add dark mode toggle --type feat

→ Labels: enhancement → Branch: feat/issue-43-dark-mode-toggle

Maintenance/chore:

/ghpm:quick-issue Update dependencies to latest versions --type chore

→ Labels: (none by default) → Branch: chore/issue-44-update-dependencies

With additional labels:

/ghpm:quick-issue Fix slow dashboard loading --label performance --label high-priority

→ Labels: bug, performance, high-priority

Issue only (no branch):

/ghpm:quick-issue Update README with new API docs --type chore --no-branch

With project association:

export GHPM_PROJECT=7
/ghpm:quick-issue Fix broken date formatting in reports

→ Issue added to project #7

</usage_examples>

<operating_rules>

• Do not ask clarifying questions. Create the issue immediately with the provided description.
• The issue description becomes both the issue title and the summary in the body.
• Labels are determined by the --type flag using standard GitHub labels:
  • fix (default) → bug label
  • feat → enhancement label
  • chore → no automatic label
• Additional labels can be added with --label flag.
• Branch names are sanitized: lowercase, special characters removed, truncated to 50 chars.
• Default type is fix (assumes most quick issues are bug fixes).
• If --no-branch is specified, skip branch creation entirely.
• On any error, provide actionable guidance for resolution. </operating_rules>

Step 1: Validate Environment

# 1. Verify gh CLI authentication
gh auth status || { echo "ERROR: Not authenticated. Run 'gh auth login'"; exit 1; }

# 2. Verify in git repository
git rev-parse --git-dir > /dev/null 2>&1 || { echo "ERROR: Not in a git repository"; exit 1; }

# 3. Verify GitHub remote exists
REPO=$(gh repo view --json nameWithOwner -q .nameWithOwner) || { echo "ERROR: No GitHub remote found"; exit 1; }
OWNER=$(gh repo view --json owner -q '.owner.login')