jira-work-links
Use when creating, correcting, or reviewing Jira links, blockers, dependency order, parent or Epic relationships, or Development references. Use also when finding pull requests or commits for a Jira issue. Do not use for a simple Jira summary that does not need relationship or development evidence, or to draft tickets from a specification; planning does that.
How do I install this agent skill?
npx skills add https://github.com/filipgutica/filip-stack --skill jira-work-linksIs this agent skill safe to install?
- Gen Agent Trust Hubpass
The skill manages Jira issue relationships and development evidence from source code repositories. It includes explicit safety instructions that limit the agent to reading and verifying data, requiring user authorization for any modifications to links. No security vulnerabilities or malicious patterns were detected.
- Socketpass
No alerts
- Snykwarn
Risk: MEDIUM · 1 issue
What does this agent skill do?
Jira work links
Use evidence from Jira and the source repository to build the smallest accurate work graph. Treat hierarchy, context, implementation, validation, and release as different relationships.
Workflow
- Read every named issue. Record its type, status, parent, description, links, and Development section before you make a change.
- Inspect the Development section first. Record each linked repository, pull request state, merge commit, commit, and build that affects the requested work.
- If the code reference is absent, search the source host for the exact Jira key. Search pull request titles, bodies, branch names, and commits. Then search by the product term, source term, and semantic equivalents.
- Trace the artifact that each issue produces or consumes. Draw the intended relationship graph before creating or removing links.
- Apply only changes the user authorized. Reading Jira and source evidence does not grant permission to edit issues, transition status, or publish links.
- Refetch every affected issue after a write. Verify the rendered relationship on both sides and report the final graph in plain language.
Relationship rules
- Use blocks only when issue A has an unfinished artifact that issue B needs. State the artifact explicitly.
- Use relates to for owning Epics, specifications, context, parallel work, and already-merged implementation that does not prevent the target from starting.
- Use parent and child relationships for scope hierarchy. Do not treat hierarchy as a dependency.
- Use duplicate only when both issues track the same required outcome.
- Do not infer dependency from issue numbers, creation order, status, ownership, or the order in which tickets were presented.
- A merged pull request proves that implementation exists. It does not prove that validation, release, or every acceptance criterion is complete.
For the Atlassian Blocks link type, issue A blocks issue B when A is the blocker
and B is the blocked issue. With createIssueLink, pass A as inwardIssue and B
as outwardIssue. After creation, Jira must render:
- On A: blocks B.
- On B: is blocked by A.
If either side renders differently, remove the incorrect link and recreate it.
Development evidence
- Prefer Jira's Development section and the authenticated source host over text pasted into a description.
- Confirm that a referenced pull request affects the ticket contract or acceptance criteria. A matching key alone is not enough.
- Record the repository, pull request URL, state, merge commit when present, and remaining validation or release work.
- If the pull request is merged but the issue remains in Verify, identify the missing validation. Do not treat the issue as Done or as a blocker yet.
- If the Development section misses a known pull request, use the repository integration's key-based association. Add a generic web link only when the integration cannot show the reference and the user requests it.
Final check
Before finishing, confirm:
- Every blocker has a named unfinished artifact.
- Owning Epics and context use
relates tounless they truly produce that artifact. - Parallel tickets do not block each other.
- Each pull request reference has a verified repository and state.
- Both sides of every dependency render in the intended direction.
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/filipgutica/filip-stack/jira-work-links">View jira-work-links on skillZs</a>