Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From mk
Create/remove/inspect JIRA issue-to-issue links (blocks, depends on, clones, relates to) via jira-as wrapper. Supports triggers like 'link KEY blocks KEY', 'what blocks KEY', 'clone KEY'. Not for sprint/epic.
How this skill is triggered — by the user, by Claude, or both
Slash command
/mk:jira-relationshipsWhen to use
Use to create / remove / inspect issue-to-issue links (blocks, depends on, clones, relates to). NOT for parent-subtask or epic-issue (mk:jira-agile).
jira-relationshipsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Forks to the `jira-relationships` agent. Link direction matters — `A blocks B` ≠ `B blocks A`. The agent confirms direction when ambiguous.
Forks to the jira-relationships agent. Link direction matters — A blocks B ≠ B blocks A. The agent confirms direction when ambiguous.
../../agents/jira-relationships.md../jira/references/{install-and-auth,cli-idioms,safety-framework}.mdreferences/relationship-patterns.md — blocker-chain analysis, sprint-planning patterns, dependency strategiesmk:jira-bulk (bulk-link via JQL — dry-run first), mk:jira-agile (epic-issue is via agile epic add, NOT here), mk:jira-search (find candidate issues via JQL before linking)npx claudepluginhub ngocsangyem/meowkit --plugin mkIssue linking, blockers, and dependency analysis. TRIGGERS: 'what's blocking', 'what is blocking', 'is blocked by', 'link issues', 'link to', 'blockers for', 'depends on', 'clone issue', 'clone with', 'blocking chain', 'dependency graph', 'show dependencies', 'get blockers', 'relates to', 'duplicates'. Use for issue dependencies, relationships, and cloning. NOT FOR: epic linking (use jira-agile), field updates (use jira-issue), bulk cloning (use jira-bulk).
Synthesizes Jira issues with context: fetches main issue, linked issues, sub-tasks, blockers, and Confluence docs. Activates on issue key mentions.