skills.rest
dokipen
dokipenCOMMUNITY
Explore all skills by this author →
GitHub

create-ticket

Create tickets in GitHub, Jira, or compatible trackers from title, description, and acceptance criteria.

1|1|Updated Mar 5, 2026
Search Tags:#automation#workflow#github#ticket#issue#acceptance-criteria
One-click install
npx skills add https://github.com/dokipen/claude-cadence --skill create-ticket-dokipen
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-ticket
Source: https://github.com/dokipen/claude-cadence/tree/main/.gemini/skills/create-ticket
Command: npx skills add https://github.com/dokipen/claude-cadence --skill create-ticket-dokipen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates ticket creation by collecting a title, description, and acceptance criteria and publishing a new issue in the configured tracker.

Core Features & Use Cases

  • Collects Title, Description, and Acceptance Criteria to standardize ticket inputs.
  • Creates a ticket in the configured issue tracker (GitHub, Jira, or compatible systems) and returns the ticket reference.
  • Stops after creation, preventing automatic implementation or changes to codebases.

Quick Start

Run the /create-ticket command with a title, a description, and acceptance criteria to create a new ticket.

Frequently Asked Questions about create-ticket

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

FAQPage Schema
How do I automate GitHub issue creation with consistent acceptance criteria?▼

Automating GitHub issue creation requires collecting a standardized title, description, and acceptance criteria to publish a new ticket. This approach enforces consistent ticket formats across repositories and returns the issue reference.

What is needed to standardize ticket inputs for project onboarding workflows?▼

Standardizing ticket inputs requires a defined title, a clear description, and specific acceptance criteria. Collecting these three elements ensures consistent issue-definition workflows and auditable ticketing across configured trackers.

Does this automated ticketing workflow support multiple issue tracker providers?▼

Automated ticketing workflows support provider detection for configured trackers like GitHub or Jira. The system identifies the compatible tracker and publishes the standardized issue directly to the configured provider.

How do I create a ticket without triggering automatic codebase changes?▼

Creating a ticket without codebase changes requires a stop-after-creation policy. This enforces safe, auditable ticketing by returning the ticket reference and preventing automatic implementation or side effects.

Can I use this workflow to generate issues across multiple repositories?▼

Generating issues across multiple repositories is supported when consistent ticket formats are required. The workflow detects the configured provider and publishes issues to standardize project onboarding across different repositories.

Why does my automated ticket creation stop after publishing the issue?▼

Automated ticket creation stops after publishing the issue due to an enforced stop-after-creation policy. This minimizes side effects and ensures safe, auditable ticketing by preventing automatic implementation following issue creation.

Related Skills

Explore More Product & Management Skills→
apacheapache
79

magpie-issue-reassess

Re-assess project issues against the default branch and produce verdicts.

Official
Advanced
polikeijipolikeiji

implement-ticket

Implement GitHub project tickets end-to-end and open a linked pull request.

Community
Advanced
yellow-seedyellow-seed

github-issue

Create GitHub issues from .github/ISSUE_TEMPLATE templates with labels and milestones.

Community
Intermediate
Dev10x-GuruDev10x-Guru
7

Dev10x:git-promote

Convert git commits into issue tracker tickets with branch management and message formatting.

Official
Intermediate