skills.rest
4armsxlr8
4armsxlr8COMMUNITY
Explore all skills by this author →
GitHub

ticket-publish

Convert local JSON ticket files to GitHub Issues using GitHub CLI.

Updated Aug 27, 2026
Search Tags:#collaboration#ticket management#GitHub#issue tracking#ticket conversion
One-click install
npx skills add https://github.com/4armsxlr8/ccx-arsenal --skill ticket-publish
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ticket-publish
Source: https://github.com/4armsxlr8/ccx-arsenal/tree/main/plugins/agent-core/skills/ticket-publish
Command: npx skills add https://github.com/4armsxlr8/ccx-arsenal --skill ticket-publish

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, and includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the process of converting local JSON tickets into GitHub Issues, facilitating smoother team collaboration and issue tracking.

Core Features & Use Cases

  • Ticket to Issue Conversion: Converts local JSON tickets into GitHub Issues with minimal effort.
  • Opt-in Workflow: Users can choose when to publish tickets, maintaining local integrity.
  • Use Case: When you want to share a ticket with your team and ensure it's tracked in GitHub, simply run the /ticket-publish command followed by the ticket ID.

Quick Start

To publish a ticket to GitHub, use the command: /ticket-publish <T-XXXX>

Frequently Asked Questions about ticket-publish

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

FAQPage Schema
How do I convert local JSON tickets to GitHub Issues?▼

You can convert local JSON tickets to GitHub Issues by running the /ticket-publish command with the specific ticket ID, which uses GitHub CLI commands to interact with the GitHub API and write the issue.

Do I need GitHub CLI installed to publish JSON tickets to GitHub Issues?▼

Yes, you need the GitHub CLI (gh) installed and configured, because this ticket conversion process relies on it to interact with the GitHub API and write issues to external repositories.

What is the best way to share local JSON tracking tickets with an external repository team?▼

The best way to share local JSON tracking tickets is using a ticket conversion tool that pushes them to GitHub Issues, ensuring team collaboration and issue tracking without compromising local integrity.

Can I choose when to publish local tickets to GitHub Issues?▼

Yes, this ticket conversion process uses an opt-in workflow, allowing you to choose exactly when to publish local JSON tickets to GitHub Issues rather than syncing automatically.

Why push local JSON tickets to GitHub Issues for team collaboration?▼

Pushing local JSON tickets to GitHub Issues streamlines team collaboration by moving internal tracking data into a shared external repository, making it easier for the entire team to track and manage issues.

Are there limitations to converting JSON files to GitHub Issues using CLI?▼

This ticket conversion is limited to JSON ticket formats and requires GitHub CLI, meaning it is suitable for internal tracking systems that need to share tickets with external repositories via GitHub Issues.

Related Skills

Explore More Software Engineering Skills→
normcrandallnormcrandall
1

JIRA Integration

Convert JIRA tickets into local story files via API or web scraping.

Community
Intermediate
drillandrillan

issue-reporter

Post formatted Markdown progress comments to GitHub Issues.

Community
Intermediate
opencueopencue
3

speckit-taskstoissues

Convert spec-kit project tasks into ordered GitHub issues.

Official
Intermediate
zero3041zero3041
1

jira-integration

Automate Jira ticket management via the Jira REST API.

Community
Intermediate