Mk jira relationships
Manage JIRA issue relationships via jira-as: link, unlink, blockers, dependencies, clone, bulk-link. NOT sprint/epic relationships (mk:jira-agile).From its SKILL.md
npx -y skills add ngocsangyem/MeowKit --skill mk-jira-relationshipsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 14 stars14 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.3 KB, 319 tokens by cl100k_base, as published. Nobody here has run it
mk:jira-relationships
Forks to the jira-relationships agent. Link direction matters — A blocks B ≠ B blocks A. The agent confirms direction when ambiguous.
Triggers
- "link PROJ-123 blocks PROJ-456"
- "what blocks PROJ-123?"
- "what does PROJ-123 depend on?"
- "clone PROJ-123 with new summary 'Follow-up'"
- "unlink PROJ-123 from PROJ-456"
Examples
- Direct link: "link PROJ-123 as blocked-by PROJ-100"
- Blocker query: "show me everything blocking PROJ-123"
- Bulk-link via JQL: "link all PROJ stories tagged 'epic-x' as part of EPIC-1" (agent will run a dry-run first)
See also
- Agent:
../../agents/jira-relationships.md - Shared:
../jira/references/{install-and-auth,cli-idioms,safety-framework}.md - Domain refs:
references/relationship-patterns.md— blocker-chain analysis, sprint-planning patterns, dependency strategies
- Peer leaves:
mk:jira-bulk(bulk-link via JQL — dry-run first),mk:jira-agile(epic-issue is viaagile epic add, NOT here),mk:jira-search(find candidate issues via JQL before linking)
Gotchas
- (none yet — grow from observed failures)
What ships with it: 1 file
6.5 KB alongside SKILL.md
references/
- relationship-patterns.md6.5 KB