Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

link-work-items

Create, change, or remove a relationship link between two GitLab work items — related, blocks, or blocked-by. Use whenever the user wants one ticket marked as blocking, blocked by, or related to another (e.g. "block api#16 on api#20", "mark these as related") rather than describing the relationship in prose.

In Manus ausführen

Überblick

Installationsbefehl

npx skills add https://github.com/zantarix/claude-code --skill link-work-items

Kopieren Sie diesen Befehl und fügen Sie ihn in Claude Code ein, um den Skill zu installieren

Quelle

zantarix/claude-code

Sterne1

Forks0

Aktualisiert2. Juni 2026 um 09:24

SKILL.md

readonly

name	link-work-items
description	Create, change, or remove a relationship link between two GitLab work items — related, blocks, or blocked-by. Use whenever the user wants one ticket marked as blocking, blocked by, or related to another (e.g. "block api#16 on api#20", "mark these as related") rather than describing the relationship in prose.

Link two GitLab work items via the relationship API. Prose like "blocked by #N" is invisible to GitLab's board and "Linked items" widget — the formal link is the source of truth.

linkType is uppercase in both APIs: RELATED | BLOCKS | BLOCKED_BY. Direction is from the source: BLOCKED_BY on source #16 means "#16 is blocked by the target".

Preferred: GitLab MCP

Use mcp__gitlab__manage_work_item with action: add_link. id and targetId both take the numeric work item ID from mcp__gitlab__browse_work_items results. Use action: remove_link to delete a link.

Fallback: glab api graphql

# 1. Resolve iid → global ID (the linked-items API takes GIDs, not iids)
SRC=$(glab api graphql -f query='query { project(fullPath: "PROJECT") { workItems(iid: "SRC_IID") { nodes { id } } } }' | jq -r '.data.project.workItems.nodes[0].id')
TGT=$(glab api graphql -f query='query { project(fullPath: "PROJECT") { workItems(iid: "TGT_IID") { nodes { id } } } }' | jq -r '.data.project.workItems.nodes[0].id')

# 2. Create the link
glab api graphql -f query="mutation { workItemAddLinkedItems(input: { id: \"$SRC\", workItemsIds: [\"$TGT\"], linkType: BLOCKED_BY }) { errors workItem { iid } } }"

# 3. Remove (e.g. wrong direction):
glab api graphql -f query="mutation { workItemRemoveLinkedItems(input: { id: \"$SRC\", workItemsIds: [\"$TGT\"] }) { errors workItem { iid } } }"

Gotchas

workItemsIds is plural (max 10 per call) in the GraphQL fallback.
Neither the MCP nor the GraphQL API can update an existing link type. To change direction, remove and re-add.

Mehr aus diesem Repository

gleiches Repository

implement-ticket

zantarix/claude-code

Work a ticket reference to completion — fetch the issue, clarify intent with the user, then plan or implement via plan mode or /plan-adr.

2026-06-041

create-merge-request

zantarix/claude-code

Create a GitLab merge request for the current branch, describing the changes made. Adds a `Closes #N` line when the work implements a ticket. If /review was run in this session and the session folder is known, posts the review to the MR as a batched draft-note review via the `gitlab:post-mr-review` skill. Use proactively whenever the user asks to create an MR or merge request.

2026-06-031

post-mr-review

zantarix/claude-code

Reconcile a prior code review against the current branch state, then publish it to the GitLab MR as a single batched review: inline diff comments for findings in files the MR changed, and a summary comment (table + findings in untouched files) for the rest. Use after a review's fixes have been applied and you want to post the review to the MR.

2026-06-031

review

zantarix/claude-code

Run all *-reviewer agents over the current changes — partitioning a large diff into cohesive chunks reviewed in parallel — then fix critical/major findings in a single pass. Stores all output under .reviews/. There is no re-run loop: the human review (local, or via the create-pull-request / create-merge-request skills) is the verifying gate; this skill's job is to surface and fix the obvious issues before that gate. Proactively use this skill to review code you've created if you have added or modified more than two functions, or whenever you complete an implementation plan.

2026-06-031

create-pull-request

zantarix/claude-code

Create a GitHub pull request for the current branch, describing the changes made. Adds a `Closes #N` line when the work implements a ticket. If /review was run in this session and the session folder is known, posts the review.md file verbatim as a comment. Use proactively whenever the user asks to create a PR or pull request.

2026-06-031

create-child-task

zantarix/claude-code

Create preparatory work as child Task work items under a GitLab ticket — e.g. "draft an ADR", "decide between options", spike research, dependency upgrades. Use when a ticket's pre-work should be tracked as sub-tasks rather than buried in the description.

2026-06-021

Quelle

zantarix

zantarix/claude-code

GitHub-Repository öffnen Creator-Repositorys ansehen

Installationsbefehl

Download

In Manus ausführen

Nützlich fürSOC

SoftwareentwicklerInformatik- und Mathematikberufe15-1252L4

name	link-work-items
description	Create, change, or remove a relationship link between two GitLab work items — related, blocks, or blocked-by. Use whenever the user wants one ticket marked as blocking, blocked by, or related to another (e.g. "block api#16 on api#20", "mark these as related") rather than describing the relationship in prose.

Link two GitLab work items via the relationship API. Prose like "blocked by #N" is invisible to GitLab's board and "Linked items" widget — the formal link is the source of truth.

linkType is uppercase in both APIs: RELATED | BLOCKS | BLOCKED_BY. Direction is from the source: BLOCKED_BY on source #16 means "#16 is blocked by the target".

Preferred: GitLab MCP

Fallback: glab api graphql

# 1. Resolve iid → global ID (the linked-items API takes GIDs, not iids)
SRC=$(glab api graphql -f query='query { project(fullPath: "PROJECT") { workItems(iid: "SRC_IID") { nodes { id } } } }' | jq -r '.data.project.workItems.nodes[0].id')
TGT=$(glab api graphql -f query='query { project(fullPath: "PROJECT") { workItems(iid: "TGT_IID") { nodes { id } } } }' | jq -r '.data.project.workItems.nodes[0].id')

# 2. Create the link
glab api graphql -f query="mutation { workItemAddLinkedItems(input: { id: \"$SRC\", workItemsIds: [\"$TGT\"], linkType: BLOCKED_BY }) { errors workItem { iid } } }"

# 3. Remove (e.g. wrong direction):
glab api graphql -f query="mutation { workItemRemoveLinkedItems(input: { id: \"$SRC\", workItemsIds: [\"$TGT\"] }) { errors workItem { iid } } }"

Gotchas

workItemsIds is plural (max 10 per call) in the GraphQL fallback.
Neither the MCP nor the GraphQL API can update an existing link type. To change direction, remove and re-add.