← Back to the catalog Manage JIRA issue relationships via the jira-as wrapper: link, unlink, blockers, dependencies, clone, bulk-link. Triggers: 'link KEY blocks KEY', 'what blocks KEY', 'clone KEY', 'unlink KEY from KEY'. NOT for sprint/epic relationships (mk:jira-agile).
View on GitHub ↗ Copy repo URL Copy SKILL.md link License: MIT /plugin marketplace add ngocsangyem/MeowKit The exact command may vary by repository. Check the README on GitHub.
For the skill author
Shows your skill is listed on Skillteca, generates a backlink and trackable traffic.
Markdown HTML
[](https://www.skillteca.com.br/skills/mk-jira-relationships?utm_source=badge&utm_medium=readme&utm_campaign=badge) Copy snippet Resources to assist in writing various internal communications, adhering to company-preferred formats. Claude should utilize this skill for status reports, leadership updates, newsletters, FAQs, and other internal documents.
DevOps e Infra by anthropics
Monitors a pull request or review cycle until it is ready to merge. This skill is used to track PR comments, reviews, and CI status until all actionable issues are resolved.
DevOps e Infra #ai by thedotmack
Execute a phased implementation plan using subagents. Use when asked to execute, run, or carry out a plan — especially one created by make-plan.
DevOps e Infra #ai by thedotmack
Token-optimized structural code search using tree-sitter AST parsing. Use this instead of reading full files when you need to understand code structure, find functions, or explore a codebase efficiently.
DevOps e Infra #ai by thedotmack
Category alert
One short email with only the new DevOps e Infra skills. 4 minutes of reading, no spam, unsubscribe with one click.
You confirm your email on the first send. No spam. Unsubscribe with one click.
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 via agile epic add, NOT here), mk:jira-search (find candidate issues via JQL before linking)
Gotchas
(none yet — grow from observed failures)
Read full description↓
Comments · No comments No comments yet. Be the first. 