ambaba/jira-maker
Create JIRA tickets from context using jira-cli. Drafts content, confirms with user, then creates.
18
Quality
18%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Securityby
Passed
No known issues
Validation failed for skills in this tile
One or more skills have errors that need to be fixed before they can move to Implementation and Discovery review.
SKILL.md
- name:
- jira-maker
- description:
- Sub-orchestrator for JIRA/Confluence operations. Routes to leaf skills based on intent. Trigger on: "make a jira", "create jira", "jira ticket", "file a ticket", "list my tickets", "confluence page".
- allowed-tools:
- Skill, Bash, Read
JIRA Maker (Sub-Orchestrator)
Routes to the appropriate leaf skill based on user intent.
Routing
| Intent | Delegate to |
|---|---|
| Create a ticket | tessl__jira-maker-create |
| Create/update Confluence page | tessl__jira-maker-confluence |
| Query/list tickets | tessl__jira-maker-query |
HARD RULE: Extract ticket from branch before asking
Before prompting for a JIRA ticket, check git branch name AND any open PR title for a ticket key (e.g., CXP-29506). If found, use it — do NOT ask.
When called by an orchestrator
Input: Problem description, solution, PR URL (optional), project key (default CXP) Output: JIRA ticket key and URL
Integration with feature-implementation-gates
When creating a JIRA before implementation:
- Create ticket with
tessl__jira-maker-create→ getCXP-XXXXX - Branch name becomes:
ambaba/CXP-XXXXX/<what-is-done> - PR body references the ticket:
Closes CXP-XXXXX
When creating a JIRA after implementation (retroactive):
- Create ticket referencing the existing PR
- Add PR link in description or as comment
Pitfalls & config
Delegate to tessl__jira-maker-pitfalls for reference or when troubleshooting.