create-ticket

Create tickets on GitHub or Jira from conversation context and save local artifacts.

1|1|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/williamthorsen/codeassembly --skill create-ticket-williamthorsen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-ticket
Source: https://github.com/williamthorsen/codeassembly/tree/main/packages/agents/content/skills/create-ticket
Command: npx skills add https://github.com/williamthorsen/codeassembly --skill create-ticket-williamthorsen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a conversation into a tracked work item requires manually choosing a platform, formatting a title and body, applying labels, linking related tickets, and keeping local records in sync. This Skill automates that entire flow so a ticket is created on the correct remote platform with consistent conventions. ## Core Features & Use Cases - Multi-platform creation: Resolves the target platform from project preferences or the git remote, then creates the ticket via GitHub (gh issue create) or Jira (connected tools or acli). - Conventional titles and labels: Renders the ticket title with describe-change.mjs using the work type and scope, and maps type/scope to GitHub labels via .meta/label-map.json. - Relationships and artifacts: Applies parent, blocked-by, and blocking relationships, persists the branch-to-ticket association, and saves ticket and plan artifacts locally with standardized frontmatter. - Use Case: While discussing a bug in a coding session, ask the agent to file it; the Skill creates a GitHub issue with the right labels, links it as blocked by another issue, and saves a local ticket artifact. ## Quick Start Ask the agent to create a ticket for the problem we just discussed, optionally with --parent or --blocked-by references.

Frequently Asked Questions about create-ticket

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

FAQPage Schema
How do I create a GitHub issue from an AI conversation?

Invoke the create-ticket skill and describe the problem; it writes the body to a scratch file and runs gh issue create with the rendered title and resolved labels. The issue number from the printed URL becomes the ticket ID.

How do I create a Jira ticket with acli from the command line?

The skill converts the body to ADF, writes it to a scratch file, and runs acli jira workitem create with the project key, issue type, and summary. The returned key becomes the ticket ID verbatim.

Can I set parent and blocking relationships when creating a ticket?

Yes, pass --parent, --blocked-by, or --blocking with ticket references like #123 or ABC-123. On GitHub they are applied with gh issue edit flags; on Jira they use link tools or acli workitem link create.

Does the skill work when no remote platform is configured?

Yes, it falls back to an auto-generated ticket ID in the form {YYYYMMDD}-{4 random hex} and saves local artifacts only. It logs a warning and reports all decided relationships as skipped.

Why are my GitHub labels not applied to the new issue?

Labels are only applied when .meta/label-map.json exists and contains entries for the ticket's type and scope. Missing entries are silently skipped, and label flags must be written as literal text in the create call.