api
Execute a raw Jira REST API call through the jirac CLI, including GET, POST, PUT, DELETE, and PATCH requests to any Jira REST…
@mulhamnaInstall SkillDevelopment
Skill
/link
Manage Jira issue links (blocks, relates, duplicates, etc.) with jirac — list link types, add a link, or delete an existing link
Claude Code
$ npx -y skills add mulhamna/jira-commands --skill link --agent claude-code
Codex
$ npx skills add mulhamna/jira-commands --skill link -a codex -y
Cursor
$ npx skills add mulhamna/jira-commands --skill link -a cursor -y
Gemini CLI
$ npx skills add mulhamna/jira-commands --skill link -a gemini-cli -y
GitHub Copilot
$ npx skills add mulhamna/jira-commands --skill link -a github-copilot -y
OpenCode
$ npx skills add mulhamna/jira-commands --skill link -a opencode -y
Windsurf
$ npx skills add mulhamna/jira-commands --skill link -a windsurf -y
SKILL.md
link.SKILL.mddescription: Manage Jira issue links (blocks, relates, duplicates, etc.) with jirac — list link types, add a link, or delete an existing link
Manage links between Jira issues using `jirac`.
Steps: 1. Check that `jirac` is available by running `jirac --version`. If missing, tell the user to install it (`cargo install jira-commands`). 2. Determine the operation from the user's request:
- **List link types**: `jirac issue link list-types`
- **Add link**: needs link type (e.g. Blocks, Relates, Duplicates), outward key (source), inward key (target).
- **Delete link**: needs the link ID (obtain it from `jirac issue view <KEY>`).
3. For unfamiliar link type names, run `jirac issue link list-types` first. 4. Run the appropriate command and report the resulting link.
Notes:
- The **outward** issue is the "source" of the link (the blocker, the duplicate). The **inward** issue is the "target" (the blocked, the original).
- Common link type names: `Blocks`, `Relates`, `Duplicates`, `Clones`, `Cloners`. Casing matters — match what `list-types` returns.
- Adding the same link twice is allowed by Jira and produces duplicate entries — check existing links via `jirac issue view <KEY>` before adding.
Examples:
- "what link types are available" → `jirac issue link list-types`
- "PROJ-1 blocks PROJ-2" → `jirac issue link add --link-type Blocks PROJ-1 PROJ-2`
- "PROJ-3 is related to PROJ-4" → `jirac issue link add --link-type Relates PROJ-3 PROJ-4`
- "PROJ-5 duplicates PROJ-6" → `jirac issue link add --link-type Duplicates PROJ-5 PROJ-6`
- "add a comment when linking" → `jirac issue link add --link-type Blocks --comment 'blocked by infra change' PROJ-1 PROJ-2`
- "delete link 10042" → `jirac issue link delete 10042`
Read more
description: Manage Jira issue links (blocks, relates, duplicates, etc.) with jirac — list link types, add a link, or delete an existing link
Manage links between Jira issues using `jirac`.
Steps: 1. Check that `jirac` is available by running `jirac --version`. If missing, tell the user to install it (`cargo install jira-commands`). 2. Determine the operation from the user's request:
- **List link types**: `jirac issue link list-types`
- **Add link**: needs link type (e.g. Blocks, Relates, Duplicates), outward key (source), inward key (target).
- **Delete link**: needs the link ID (obtain it from `jirac issue view <KEY>`).
3. For unfamiliar link type names, run `jirac issue link list-types` first. 4. Run the appropriate command and report the resulting link.
Notes:
- The **outward** issue is the "source" of the link (the blocker, the duplicate). The **inward** issue is the "target" (the blocked, the original).
- Common link type names: `Blocks`, `Relates`, `Duplicates`, `Clones`, `Cloners`. Casing matters — match what `list-types` returns.
- Adding the same link twice is allowed by Jira and produces duplicate entries — check existing links via `jirac issue view <KEY>` before adding.
Examples:
- "what link types are available" → `jirac issue link list-types`
- "PROJ-1 blocks PROJ-2" → `jirac issue link add --link-type Blocks PROJ-1 PROJ-2`
- "PROJ-3 is related to PROJ-4" → `jirac issue link add --link-type Relates PROJ-3 PROJ-4`
- "PROJ-5 duplicates PROJ-6" → `jirac issue link add --link-type Duplicates PROJ-5 PROJ-6`
- "add a comment when linking" → `jirac issue link add --link-type Blocks --comment 'blocked by infra change' PROJ-1 PROJ-2`
- "delete link 10042" → `jirac issue link delete 10042`
Ships withjira-commands
Jira on the command line. jirac is a Jira command-line client written in Rust. It ships as a single binary with no runtime dependencies and runs on macOS, Linux, and Windows.
5429 skills
Stars on GitHub
Momentum
- stars in total
- 54
Other skills on jira-commands.
@mulhamnaInstall Skillbatch
Run mixed Jira operations (create, update, transition, archive) from a single JSON manifest file using jirac batch
@mulhamnaInstall Skillbulk-comment
Add the same Markdown comment to multiple Jira issues with jirac, either by JQL query or explicit issue keys
@mulhamnaInstall Skillbulk-create
Create multiple Jira issues at once from a JSON manifest file using jirac bulk-create
@mulhamnaInstall SkillMore skills from other plugins.
Auto-invoked
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
@obraInstall Skillask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
@mattpocockInstall SkillAuto-invoked
Questions about link.
- Which coding agents can use link?
- link installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.