create-jira-item
Skill8 starsChanged 3 months agoMITView on GitHub
Create Jira issues (stories, epics, initiatives) with custom field introspection to fill org-specific fields correctly. Use when the user asks to create a Jira ticket, story, epic, initiative, or task.
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 4 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Create Jira issues using the Atlassian MCP, with proper custom field handling.
- Very specific: line 12
Project: Use the project specified by the user.
- Distinctive: line 17
Before creating the issue, discover the project's field requirements:
- Distinctive: line 36
All required custom fields populated from step 2
- Distinctive: line 40
If the issue should be under an epic:
- Very specific: line 41
Use createIssueLink or set the epic link field (varies by Jira config)
- Very specific: line 42
If the user mentions an epic by name or key, search for it first via searchJiraIssuesUsingJql(cloudId, "project = X AND issuetype = Epic …
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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 Jira Item
Create Jira issues using the Atlassian MCP, with proper custom field handling.
1. Determine Target
- Project: Use the project specified by the user. If not specified, infer by searching the user's recent issues (
searchJiraIssuesUsingJqlwith(assignee = currentUser() OR reporter = currentUser()) ORDER BY updated DESC). If inference fails, ask. - Issue type: story, epic, task, initiative, etc. Infer from context or ask.
2. Introspect Custom Fields
Before creating the issue, discover the project's field requirements:
- Get available issue types via
getJiraProjectIssueTypesMetadata(cloudId, projectIdOrKey). - Get field metadata for the chosen issue type via
getJiraIssueTypeMetaWithFields(cloudId, projectIdOrKey, issueTypeId). - Pay attention to:
- Required fields that are not standard (e.g., "Team", "Quarter", "Initiative Link", "Sprint")
- Custom field IDs (
customfield_NNNNN) -- use these in the create call - Allowed values for select/multi-select fields
For epics and initiatives especially, org-specific fields are common and must be populated. Do not rely on default field assumptions.
3. Create the Issue
Use createJiraIssue with:
- Summary: terse, descriptive title
- Description: terse. Bullet points preferred. No boilerplate.
- Assignee: current user (use
lookupJiraAccountIdif needed) - Priority: Medium unless user specifies otherwise
- All required custom fields populated from step 2
4. Link to Epic (if applicable)
If the issue should be under an epic:
- Use
createIssueLinkor set the epic link field (varies by Jira config) - If the user mentions an epic by name or key, search for it first via
searchJiraIssuesUsingJql(cloudId, "project = X AND issuetype = Epic AND summary ~ 'name'").
5. Report
Return the issue key and URL. If any required fields were unknown or couldn't be populated, note them.
In this repository38 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- active-readSkill
- active-reviewSkill
- analyze-knowledgeSkill
- audit-accomplishmentsSkill
- audit-historySkill
- bisectSkill
- ci-debug-loopSkill
- create-decision-documentSkill
- create-prSkill
- create-ruleSkill
- create-skillSkill
- discover-patternsSkill
- evaluate-dependencySkill
- fix-pr-conflictSkill
- implement-planSkill
- match-voiceSkill
- push-and-watchSkill
- rebase-pr-chainSkill
- review-allSkill
- review-api-compatSkill
- review-ciSkill
- review-codeSkill
- review-coverageSkill
- review-databaseSkill
- review-documentationSkill
- review-infrastructureSkill
- review-observabilitySkill
- review-performanceSkill
- review-planSkill
- review-reliabilitySkill
- review-securitySkill
- review-trajectorySkill
- set-session-contextSkill
- ship-itSkill
- simplify-proseSkill
- start-daySkill
- verify-when-completeSkill
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.

