Back to skills
SkillHub ClubShip Full StackFull Stack
jira-write-ticket
Use when asked to write a Jira ticket.
Packaged view
This page reorganizes the original catalog entry around fit, installability, and workflow context first. The original raw source lives below.
Stars
10
Hot score
84
Updated
March 20, 2026
Overall rating
C2.2
Composite score
2.2
Best-practice grade
A92.0
Install command
npx @skill-hub/cli install bkircher-skills-jira-write-ticket
Repository
Best for
Primary workflow: Ship Full Stack.
Technical facets: Full Stack.
Target audience: everyone.
License: Unknown.
Original source
Catalog source: SkillHub Club.
Repository owner: bkircher.
This is still a mirrored public skill entry. Review the repository before installing into production workflows.
What it helps with
- Install jira-write-ticket into Claude Code, Codex CLI, Gemini CLI, or OpenCode workflows
- Review https://github.com/bkircher/skills before adding jira-write-ticket to shared team environments
- Use jira-write-ticket for development workflows
Works across
Claude CodeCodex CLIGemini CLIOpenCode
Favorites: 0.
Sub-skills: 0.
Aggregator: No.
Original source / Raw SKILL.md
--- name: jira-write-ticket description: Use when asked to write a Jira ticket. --- Generate a Jira ticket description and acceptance criteria using simple Markdown. Strictly follow this order: - If information is missing or unclear, state this and add numbered, targeted clarification questions. - Convert any code locations mentioned to GitHub permalinks (e.g., https://github.com/<repo>/blob/<commit>/<file>#L<line>) when possible. If not possible, note this and request more details. - Find and scan the necessary code to gain more context. - For referenced Jira tickets, use the jira-read-ticket skill to fetch and summarize details, and include them in a `### Links` section. Once all question have been clarified follow this structure: ## Description - Begin with a concise summary based on the provided details. ### Links (if applicable) - List all referenced Jira tickets with summaries where available. - Explicitly note missing or unfetched references. ## Acceptance Criteria - Present concise, bulleted acceptance criteria. Organize as directed by the user or logically. **Section Order:** Always use this order: Description, Links (if any), Acceptance Criteria. - Present every section, even if empty; include guidance or clarification questions as needed. - Number clarification questions. ## Output Format Use only the following Markdown template, maintaining strict section order: ```markdown ## Description <Concise ticket summary, or notes/questions if info is missing/unclear> ### Links (if applicable) - <Linked ticket 1> ## Acceptance Criteria - <Acceptance criterion 1> - <Acceptance criterion 2> - ... ``` - Only use this template. For sections lacking information, call this out and supply numbered clarification questions. - State and ask if code locations cannot be converted to GitHub permalinks.