gitlab-board-sync

Name: gitlab-board-sync
Author: nextstage-brasil

github.com/nextstage-brasilProductivity047 installsUpdated 5d ago

About gitlab-board-sync

gitlab-board-sync is a skill for mirroring local SDD planning and execution state to existing GitLab issues. It guides issue reads and carefully staged updates without creating issues.

Key features

01Read issue descriptions and comments
02Batch-update milestones, labels, assignees, estimates
03Sync task start and completion status
04Record spent time and internal notes

Use cases

01Review linked issues before implementation
02Apply planned work details to mapped issues
03Keep issue status aligned with task execution

MCP support

Requires a GitLab MCP server and directs tool calls through mcp-gitlab-usage. It uses GitLab issue-reading and update tools; it does not create issues.

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/nextstage-brasil/skills --skill gitlab-board-sync

After installing, type/gitlab-board-syncin Claude Code to confirm it loaded.

Bundled filesevals/evals.jsonreferences/gitlab-sync-config.template.md

Details

From the project README

GitLab Board Sync

Mirror local SDD planning/execution state onto existing GitLab issues. Does not create issues.

Prerequisites

GitLab MCP available — follow mcp-gitlab-usage for all tool calls
If multiple GitLab MCP servers: ask human which to use
{product_root}/docs/context/gitlab-sync-config.md validated
For post-planning batch: gitlab-issue-feature-map.md exists

Configuration

Read references/gitlab-sync-config.template.md for expected fields:

project_id, milestone_id, assignee_default
status_backlog, status_in_progress, status_done, status_blocked
rf_label_format, base_branch, work_branch, mr_target_branch

Discover unknown status labels via list_project_labels — confirm with human.

Flow C — Pre-implementation read

When task lists GitLab issue IIDs:

read_issue for description + recent comments
Non-blocking if inaccessible — log warning, continue
Do not mutate issue in this flow

Flow A — Post-planning batch

Per issue in map (excluding exclude_issues):

Validate milestone (project + group)
update_issue with milestone_id
One set_issue_labels — remove_labels + add_labels atomically (RF, Status, Equipe)
assign_issue
set_issue_estimate from linked task header (seconds)

Flow B — Per-task execution sync

Task start (before coding)

remove: status_backlog
add: status_in_progress

Record start time for add_issue_spent_time.

Task complete (after validation)

Only if already status_in_progress:

remove: status_in_progress
add: status_done, RF: NNN
add_issue_spent_time
add_issue_comment (internal=true)

Never backlog → done in one step.

Anti-patterns

Wrong	Right
`assignee` on `update_issue`	`assign_issue`
Two label calls for one transition	Single atomic `set_issue_labels`
Manual `Milestone:` label	`milestone_id` on `update_issue`
`set_issue_estimate` for time spent	`add_issue_spent_time`
Public comment for internal notes	`internal: true`

References

File	When
`references/gitlab-sync-config.template.md`	Bootstrap config
`mcp-gitlab-usage`	Tool schemas and gates

Comments

Markdown supported

Details

Author: nextstage-brasil
Repository: nextstage-brasil/skills
Category: Productivity
Installs: 47
GitHub stars: 0

Report

More skills

All skills

lark-base

open.feishu.cn

830.7k

Operate on Feishu Base: create tables, fields, records, and views; handle statistics, formulas/lookups, forms, dashboards, app mode (BaseApp/AppMode pages and components), Workspace directories, workflows, role permissions, and the template center (Base template categories, lists, and search). Use when encountering Base/multidimensional tables/bitable, BaseApp/AppMode, or /base/ or /app/ links. Do not use lark-apps for BaseApp; route file import/export to lark-drive and authentication/authorization to lark-shared.

lark-drive

open.feishu.cn

830.7k

Feishu cloud storage (Drive): manage Drive files and folders, including uploads/downloads, folder creation, copying/moving/deleting, viewing metadata, checking permission settings, comments/permissions/subscriptions, titles, versions, Feishu document security labels (secure labels), and local file imports. Use when users need to organize Drive folders, handle cloud storage resource URLs/tokens, identify link types/actual tokens/titles, or import Word/Markdown/Excel/CSV/PPTX/.base as docx/sheet/bitable/slides. Route doubao.com cloud storage URLs/tokens by resource path and token too; do not fall back to WebFetch. Not responsible for: editing document content (use lark-doc), spreadsheet/Base table data operations (use lark-sheets/lark-base), knowledge space node/member management (use lark-wiki), or native Markdown file read/write/patch/diff (use lark-markdown).

lark-shared

open.feishu.cn

830.5k

Use for lark-cli setup/auth tasks: auth login/status/logout, user vs bot identity, business-domain permissions (--domain, including all/docs/drive), missing scopes, revoking authorization, or handling _notice JSON.

lark-im

open.feishu.cn

829.7k

Feishu instant messaging: send and receive messages and manage group chats. Send and reply to messages, search chat history, manage group members, upload and download images and files, manage emoji reactions, send urgent notifications in-app/by SMS/by phone, send and handle Interactive Cards, and listen for card button callbacks (card.action.trigger). Use when users need to send messages, view or search chat history, download chat files, view group members, search groups, create group or topic chats, manage marker data, manage Feed pins (add/remove/search pinned conversations), manage tag data, or handle card callbacks.