jira-kickoff

Confirm or create Jira issues and prepare safe Git branches.

8|1|Updated Mar 1, 2026
One-click install
npx skills add https://github.com/JoeCP17/LLM-Dot-files --skill jira-kickoff
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jira-kickoff
Source: https://github.com/JoeCP17/LLM-Dot-files/tree/main/codex/skills/jira-kickoff
Command: npx skills add https://github.com/JoeCP17/LLM-Dot-files --skill jira-kickoff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents implementation from starting before the correct Jira issue is ready and a Git working branch is safely created from an up-to-date main branch.

Core Features & Use Cases

  • Existing Jira kickoff: Reads a provided Jira issue key, uses the issue type to select the branch prefix, and generates a branch name from the Jira title.
  • New Jira kickoff from requirements: Validates the target Jira project key and supported issue types, drafts a Korean default title/description, and creates the issue only after explicit approval.
  • Git safety-first branching: Enforces a clean working tree, updates local main from origin with fast-forward only, checks for local and remote branch collisions, and only then creates and checks out the approved branch.

Use case: You have rough changes to implement but want to ensure the Jira ticket, branch naming convention, and main synchronization are handled correctly before touching code.

Quick Start

Use the jira-kickoff skill with your project key and rough requirements, then confirm the proposed Jira draft and final branch name when prompted.

Frequently Asked Questions about jira-kickoff

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

FAQPage Schema
How do I create a Git working branch from a Jira issue safely?

To create a Git working branch from a Jira issue safely, the skill reads your issue key, selects a branch prefix based on the issue type, and generates a branch name from the Jira title. It enforces a clean working tree before creating the branch.

What is the best way to draft a new Jira issue from rough requirements?

Drafting a new Jira issue from rough requirements involves validating the target project key and supported issue types, then drafting a default title and description. The issue is created only after you provide explicit approval of the draft.

How do I prevent branch name collisions when starting implementation work?

Preventing branch name collisions when starting implementation work requires checking both local and remote branches for conflicts. The skill performs collision checks and synchronizes local main from origin using fast-forward only before checking out the approved branch.

How do I synchronize local main from origin before creating a feature branch?

Synchronizing local main from origin before creating a feature branch requires enforcing a clean working tree and updating local main with fast-forward only. This ensures your implementation work starts from an up-to-date and safe main branch.

Do I need an existing Jira ticket to generate a working branch?

You do not need an existing Jira ticket to generate a working branch. The skill supports existing Jira-based development flows and new Jira drafting flows where a project key and requirements must be validated and converted into an issue plus an approved branch.

Why does Jira site resolution need to be unambiguous for branch creation?

Jira site resolution needs to be unambiguous for branch creation to ensure the correct project key and issue are validated. Strict draft approval for new issues prevents implementation from starting before the correct Jira issue is ready.