tickets-batch

Batch-file tickets from a shared context into separate GitHub issues.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/AAbdulghany/fms --skill tickets-batch-aabdulghany
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tickets-batch
Source: https://github.com/AAbdulghany/fms/tree/main/.claude/skills/tickets-batch
Command: npx skills add https://github.com/AAbdulghany/fms --skill tickets-batch-aabdulghany

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the creation of multiple GitHub issues in a single session, reducing repetitive manual steps and ensuring consistent ticket structure.

Core Features & Use Cases

  • Bulk batch creation of 5–20 tickets from a shared context, with per-ticket micro-interviews.
  • Enforces each ticket body to conform to the project’s ticket schema, including optional parent references.
  • Provides a safety pre-commit batch confirmation to prevent accidental filing and partial state changes.

Quick Start

Provide a bulk list of ticket titles or a path to a markdown file, and let the skill normalise them into a batched filing workflow.

Frequently Asked Questions about tickets-batch

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

FAQPage Schema
How do I batch-create multiple GitHub issues at once?▼

Batch-create 5–20 GitHub issues by providing a bulk list of ticket titles or a markdown file path, and the skill normalises them into a batched filing workflow with per-ticket micro-interviews.

What's the best way to file bulk project-management tickets across multi-project repositories?▼

File bulk tickets across multi-project repositories by resolving the target repo and normalising input to generate per-ticket bodies that conform to the project's ticket schema.

Can I enforce a consistent ticket schema when creating GitHub issues in bulk?▼

Yes, GitHub issues created in bulk are enforced to conform to the project's ticket schema, including optional parent references, required sections, and labeling driven by configuration.

Do I need a configuration file to batch-file GitHub issues with consistent priority and labels?▼

You need a .claude/project-config.json file defining the whitelist, priority scheme, and required sections to drive labeling and structure during batch GitHub issue creation.

How does the pre-commit batch confirmation prevent accidental filing of GitHub issues?▼

A safety pre-commit batch confirmation step prevents accidental filing and partial state changes by requiring approval before the batch of GitHub issues is submitted.

Does tickets-batch support generating GitHub issue bodies with optional parent references?▼

Yes, tickets-batch supports optional parent references by generating per-ticket bodies that conform to the ticket schema during the batch GitHub issue creation workflow.