create-jira-issue
Skill2 starsChanged 19 days agoApache-2.0View on GitHub
Create a new Jira issue with proper linking, semantic code search for context, and team notification. Use when user says "create Jira", "file a bug", "new issue", or "create ticket".
2 other projects use a version of this.
Adopted by
Most recently taken up by
- henrilhos/skillstheir own version, first seen Oct 17, 2026
- couimet/my-claude-skillstheir own version, first seen Aug 19, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- couimet/my-claude-skills★ 1same name
- henrilhos/skills★ 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 repository124 other files it gives its agents.
- add-projectSkill
- ansible-configure-vmSkill
- api-smoke-testSkill
- appinterface-checkSkill
- attach-session-to-jiraSkill
- aws-rds-debugSkill
- beerSkill
- bootstrap-all-knowledgeSkill
- bootstrap-knowledgeSkill
- build-persona-styleSkill
- cancel-pipelineSkill
- cert-checkSkill
- check-ci-healthSkill
- check-integration-testsSkill
- check-mr-feedbackSkill
- check-my-prsSkill
- check-secretsSkill
- ci-retrySkill
- cleanup-branchesSkill
- cleanup-stale-executionsSkill
- clone-jira-issueSkill
- close-issueSkill
- close-mrSkill
- cloud-inventorySkill
- coffeeSkill
- compare-optionsSkill
- create-mrSkill
- create-slide-deckSkill
- data-migration-verifySkill
- debug-local-dbSkill
- debug-prodSkill
- deploy-to-ephemeralSkill
- dev-workflow-orchestratorSkill
- discovered-work-summarySkill
- edit-slide-deckSkill
- email-digestSkill
- environment-overviewSkill
- explain-codeSkill
- export-presentationSkill
- extend-ephemeralSkill
- find-similar-codeSkill
- gather-contextSkill
- gdrive-researchSkill
- gke-cluster-opsSkill
- hello-worldSkill
- hotfixSkill
- inscope-researchSkill
- investigate-alertSkill
- investigate-service-issuesSkill
- investigate-slack-alertSkill
- jira-hygiene-allSkill
- jira-hygieneSkill
- knowledge-refreshSkill
- konflux-statusSkill
- learn-architectureSkill
- learn-patternSkill
- list-presentationsSkill
- local-build-testSkill
- local-dev-environmentSkill
- manage-local-servicesSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 66
If notify_team: skill_run(skill_name="notify_team", inputs='{"message": "New {type} created: {key} - {summary}", "type": "info"}')
- Very specific: line 70
If "project not found": learn_tool_fix("jira_create_issue", "project not found", "Project key incorrect", "Verify project key")
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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 Issue
Creates Jira issues with:
- Semantic code search for related code (adds file references to description)
- Linking to related issues
- Slack notification to team channel
Inputs
| Input | Type | Default | Purpose |
summary | string | required | Issue summary/title |
description | string | "" | Issue description (markdown) |
issue_type | string | Task | Bug, Task, Story, Sub-task |
project | string | AAP | Jira project key |
repo | string | automation-analytics-backend | Repository for code search |
search_code | bool | true | Search codebase for related code |
notify_team | bool | true | Send Slack notification |
labels | string | - | Comma-separated labels |
priority | string | normal | blocker, critical, major, normal, minor |
link_to | string | - | Issue key to link to |
link_type | string | relates to | relates to, blocks, is blocked by, duplicates |
start_progress | bool | false | Transition to In Progress immediately |
user_story | string | - | For Story type: "As a..., I want..., so that..." |
acceptance_criteria | string | - | For Story type |
components | string | - | Comma-separated (e.g., Automation Analytics) |
Workflow
1. Load Persona
persona_load(persona="developer")
2. Knowledge & Known Issues
check_known_issues(tool_name="jira", error_text="")knowledge_query(project="automation-analytics-backend", persona="developer", section="patterns")
3. Semantic Code Search (if search_code=true)
code_search(query=summary, project=repo, limit=5)— Find related code- Parse results: extract file paths, modules, relevance scores
- Build enhanced description: append "Related Code" section with file references
4. Create Issue
jira_create_issue(project=project, summary=summary, description=enhanced_description, problem_description=description or summary, issue_type=issue_type, priority=priority, labels=labels, user_story=user_story, acceptance_criteria=acceptance_criteria, components=components)- Parse result: extract issue_key (AAP-XXXXX pattern)
5. Link Issues (if link_to)
jira_add_link(from_issue=created_issue_key, to_issue=link_to, link_type=link_type)
6. Update Labels (if inputs.labels)
jira_update_issue(issue_key=created_issue_key, fields="labels", values=labels)
7. Transition (if start_progress)
jira_transition(issue_key=created_issue_key, transition="Start Progress")
8. Get Final State
jira_view_issue(issue_key=created_issue_key)
9. Memory & Notify
memory_session_log(action="Created Jira issue {key}", details=summary)memory_append(key="state/current_work", list_path="active_issues", item={key, status, type, summary})- If notify_team:
skill_run(skill_name="notify_team", inputs='{"message": "New {type} created: {key} - {summary}", "type": "info"}')
10. Learning from Failures
- If "unauthorized":
learn_tool_fix("jira_create_issue", "unauthorized", "Jira auth failed", "Check Jira credentials") - If "project not found":
learn_tool_fix("jira_create_issue", "project not found", "Project key incorrect", "Verify project key")
Output Format
## 🎫 Create Jira Issue
### ✅ Issue Created
**Key:** [AAP-12345](https://issues.redhat.com/browse/AAP-12345)
**Summary:** ...
**Type:** Task
**Priority:** normal
**Team notified:** ✅
**Linked to:** [AAP-12344](link) (relates to)
### Next Steps
- jira_view_issue(issue_key='AAP-12345')
- skill_run("start_work", '{"issue_key": "AAP-12345"}')Key MCP Tools
persona_load,code_search,jira_create_issue,jira_add_link,jira_update_issue,jira_transition,jira_view_issue,memory_session_log,memory_append,skill_run,learn_tool_fix,check_known_issues,knowledge_query
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.

