jira-ticket
Skill1 starsChanged 6 days agoMITView on GitHub
Draft a copy-pasteable JIRA ticket from the current discussion. Use when asked to write, draft, or prepare a ticket for filing.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- kingkong0905/my-claude-codetheir own version, first seen Oct 9, 2026
- Jiplet/wiki-to-tickettheir own version, first seen Sep 4, 2026
- flurdy/agent-skillstheir own version, first seen Aug 9, 2026
- muhammadrivaldy/agent-skillstheir own version, first seen Jun 30, 2026
- sarveshtalele/mcp-skills-registrytheir own version, first seen Jun 12, 2026
- merchako/agent-skillstheir own version, first seen Jun 9, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- flurdy/agent-skills★ 9same name
- sarveshtalele/mcp-skills-registry★ 2same name
- Jiplet/wiki-to-ticket★ 1same name
- kingkong0905/my-claude-code★ 1same name
- merchako/agent-skills★ 0same name
- muhammadrivaldy/agent-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository4 other files it gives its agents.
- commit-prSkill
- implement-ticketSkill
- improve-codebaseSkill
- review-branchSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 29
Put the title and description in separate fenced code blocks, using a markdown fence for the description.
“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
JIRA ticket
Turn the discussion into a JIRA ticket a teammate can understand without reading the conversation. Propose only; do not create the ticket.
Content
Describe the problem, intended outcome, and any agreed approach. Make clear what completing the work means.
Let the work determine the structure and level of detail. Include acceptance criteria, scope boundaries, open questions, or relevant examples when they clarify the work. A simple change may need only a paragraph; do not add sections merely to fill a template.
Distinguish agreed decisions from suggestions and open questions. When the intended work is an investigation, describe what it should resolve.
Stay within the discussed scope. Do not invent requirements, commitments, assignees, or priorities. Include material assumptions and uncertainty in the description. Read code only to confirm a path or name you cite.
Required details
Include these details in every ticket, in addition to the description of the work.
- Include a T-shirt size in the description. Do not include story points.
- End the description with an
AI-assisted by:line naming the drafting agent.
Output
Put the title and description in separate fenced code blocks, using a markdown fence for the description.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.