new-ticket

Creates GitHub Project board tickets interactively with proposed type, priority, and AREA-NNN-slug identifiers.

Updated Nov 1, 2024
One-click install
npx skills add https://github.com/mlorentedev/dotfiles --skill new-ticket-mlorentedev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: new-ticket
Source: https://github.com/mlorentedev/dotfiles/tree/main/harness/skills/new-ticket
Command: npx skills add https://github.com/mlorentedev/dotfiles --skill new-ticket-mlorentedev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Filing well-formed tickets on a GitHub Projects board is repetitive and error-prone: IDs collide across parallel sessions, field and option IDs drift when hardcoded, and board listings silently truncate. This Skill turns a title into a board-ready issue with consistent Status, Priority, Type, labels, and a stable AREA-NNN-slug identifier. ## Core Features & Use Cases - Suggestion-first interactive flow: Proposes home repo, AREA prefix, Type, Priority, labels, and the next free NNN, then confirms with the human via AskUserQuestion before creating anything. - Deterministic board setup: Creates the issue with gh, adds it to the project, resolves field/option IDs at runtime, and sets Status, Priority, Type, and the ID text field. - Concurrency and verification hardening: Re-scans issue titles via paginated REST before creating, verifies results by node ID instead of truncated board listings, and defines yield rules for duplicate-ID collisions. - Use Case: You spot out-of-scope work mid-change and say "file an issue on the board" — the Skill proposes HARNESS-017-ticket-templates as a P2 chore in dotfiles, you confirm, and the ticket lands on the bitácora with all fields set. ## Quick Start Ask the agent to create a new ticket for the issue you found, for example by saying "new ticket: fix the drift assertion on Windows setup".

Frequently Asked Questions about new-ticket

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a GitHub Project board ticket from the CLI?

Use gh issue create to open the issue, gh project item-add to place it on the board, then gh project item-edit to set single-select fields like Status, Priority, and Type. Resolve field and option IDs at runtime with gh project field-list rather than hardcoding them.

How do I set custom fields on a GitHub Projects v2 item?

Run gh project field-list to get field and option IDs, then call gh project item-edit with the item ID, project ID, field ID, and single-select option ID. Text fields use the --text flag instead of an option ID.

Why does gh project item-list miss items on large boards?

gh project item-list returns items oldest-first and silently stops at its --limit, so items past the cutoff appear absent. Verify a specific item by its node ID with a GraphQL node query instead of listing the board.

How do I avoid duplicate ticket IDs when parallel sessions create issues?

Re-scan existing issue titles with the paginated REST API immediately before creating, not minutes earlier when the proposal was computed. After creating, re-run the scan and renumber promptly if a duplicate raced in.

When should I not file a ticket on the board?

Skip ticket creation for work you are doing right now in the current change, in-spec tasks tracked in a spec's tasks.md, and trivial side comments you can handle inline. The board is for work that needs triage and scheduling.