git-ticketlisted

Use when the user wants to open a GitHub issue or pull request, a GitLab issue or merge request, or any forge ticket from their case/context — "create a github issue", "open a PR", "raise a MR", "file a bug", "open a merge request", "make a pull request for this branch". Also use when they mention a house title convention like `[API/{MODULE}] summary`, or when a forge CLI is missing/unauthed and they need a title + markdown body to paste in manually. Covers GitHub (gh) and GitLab (glab); unknown hosts (Bitbucket, self-hosted) fall back to markdown. Also use for GitHub Projects v2 board actions — "close this ticket", "close issue #N", "move this to In Progress", "advance this card to Ready", "move #N to Done" — scoped to the project linked to the current repo. GitHub only for now.
itsgitz/agent-skills · ★ 0 · Code & Development · score 75

Install: claude install-skill itsgitz/agent-skills

# Git Ticket ## Overview Turns a user's case/context into a **forge ticket** — a GitHub issue/PR or GitLab issue/MR — and creates it via the forge CLI when possible. When the CLI is missing, unauthenticated, the host is unsupported, or the user declines, it **falls back** to printing the title + a ready-to-paste markdown body. It never hard-fails and never creates silently: the draft is always shown and confirmed before anything is pushed to the remote. "Ticket" is deliberately generic — one flow spans issues, PRs, and MRs, with room to add new forges (Bitbucket, self-hosted) later. Bodies are kept **simple by default** — a few sentences of prose, headings only when there's real content to put under them. Ticket length matches the change's size. ## When to Use - "Create/open a GitHub issue" or "open/raise a PR / pull request" - "Open a GitLab MR / merge request" or "file a GitLab issue" - "Make a PR for my current branch", "file a bug about X" - User has a bug report, feature request, or a finished branch to propose - Team uses a title convention (e.g. `[API/{MODULE}] summary`) and wants it applied consistently - No forge CLI / not authed → user wants a title + markdown body to paste ## When NOT to Use - Writing the **commit message** itself → that's a commit task, not a ticket - Editing or commenting on an **existing** issue/PR/MR → use `gh`/`glab` directly; this skill is for creating new ones - Pure local git work (branching, rebasing, staging) with no remote ar