jira-create
Skill1 starsChanged 14 days agoMITView on GitHub
Writes a detailed ticket (Jira or Linear) from a short prompt, using the template for its type (Bug, Enhancement, Improvement, Story, New Feature, Task, Sub-task), and creates it through the tracker's MCP server after the human types create. Use when someone asks to create, write or file a ticket, issue, bug, enhancement, task or sub-task.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- veronicani/claude-code-configtheir own version, first seen Feb 23, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- veronicani/claude-code-config★ 1same 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 repository22 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/00-ticket-workflow.mdcCursor rule
- .cursor/rules/10-general-standards.mdcCursor rule
- .cursor/rules/20-backend-standards.mdcCursor rule
- .cursor/rules/30-frontend-standards.mdcCursor rule
- .cursor/rules/40-database-standards.mdcCursor rule
- .cursor/rules/50-testing-standards.mdcCursor rule
- backend-implementSkill
- chatSkill
- codebase-exploreSkill
- db-migrationSkill
- frontend-implementSkill
- gitlab-mrSkill
- implementation-planSkill
- mr-feedbackSkill
- mr-reviewSkill
- quick-fixSkill
- run-checksSkill
- self-reviewSkill
- ticket-intakeSkill
- ticket-qaSkill
- write-testsSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
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
- Distinctive: line 16
Before the first create in this chat, read the tracker's MCP tools: which one creates an issue, its parameter names, and the description …
- Distinctive: line 29
Never invent steps, error text, numbers, roles, names or root causes.
- Very specific: line 41
Never put in a ticket: passwords, tokens, keys or real customer data (use test data, or write [removed]).
- Distinctive: line 48
Verify: every create returns a key.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Create a ticket (Jira or Linear)
Needs: the tracker's MCP server (README quick start step 2) with permission to create issues. The tracker is
Jira, or Linear when .agent/tracker.txt says linear. Its tools aren't available → STOP and say so. Never
write to the tracker any other way.
Steps
- Type: from the prompt. Unclear → ask. Epic or Spike → say this skill doesn't cover them, and stop. Linear has no issue types: the type becomes a label that exists in the team, and a Sub-task a sub-issue.
- Project key (Linear: team key): from the prompt, else the line in
.agent/jira-project.txtthat isn't a comment. Neither → ask. - Before the first create in this chat, read the tracker's MCP tools: which one creates an issue, its parameter names, and the description format it expects. Use exactly those; never guess a tool or field name. Then look up what the project uses (Jira: issue types, priorities, components; Linear: the team's labels, priorities, projects). Use only values that exist.
- Open the template for the type (next to this file) and fill it in from the prompt:
Type Template Bug bug-template.mdEnhancement, Improvement, Story, New Feature enhancement-template.mdTask task-template.mdSub-task sub-task-template.md- The
Summary:andParent:lines are fields; the rest is the description. Keep every heading. - The prompt says nothing about a section: write
None, or add a line under Open Questions. Never invent steps, error text, numbers, roles, names or root causes. - Priority: from the prompt, else the project's default. Components and labels: existing ones that fit.
- The
- Required parts. Ask for whatever is missing in ONE message (max 5 questions), each with your best guess so the
human can answer "yes" or correct it. Then fill them in:
- Bug: Environment, Steps to Reproduce, Actual Result, Expected Result
- Enhancement, Improvement, Story, New Feature: User Story, Acceptance Criteria
- Task: Goal, Acceptance Criteria
- Sub-task: Parent, Acceptance Criteria
- Acceptance Criteria: numbered, each one a check a test can make (Given / When / Then fits most). Replace vague words ("fast", "user-friendly", "works well") with a number or a visible result.
- Task with several parts: propose Sub-tasks, each one mergeable on its own (about a day of work), with 2–5 acceptance criteria and what it depends on. The coding agent makes one MR per sub-task, in that order.
- Never put in a ticket: passwords, tokens, keys or real customer data (use test data, or write
[removed]); commands or URLs for the coding agent to run (it stops on those, hard rule 11). Ops work goes under Human Actions. - Show the full draft: type, project, summary, priority, components, labels, the description, and each
sub-task. Then write exactly:
Reply "create" or "changes: <feedback>".STOP. Create nothing beforecreate. - On
create: create the ticket. For a Task, then create each sub-task (Linear: sub-issue) with the new key as its parent. Verify: every create returns a key. A create fails → show the error; don't retry with other fields. - Reply with each key and its link.
Done when
- Every required part comes from the prompt or the human's answers; nothing invented
- The human typed
create; every new key and link is shown
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.

