Menu
Use when waiting for MR merge and trigger MR pipelines using glab CLI helpers
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
| name | mr-pipeline |
| description | Use when waiting for MR merge and trigger MR pipelines using glab CLI helpers |
| license | MIT |
| compatibility | opencode |
| metadata | {"audience":"developers","author":"pedropombeiro","workflow":"gitlab"} |
Helper scripts for coordinating GitLab merge request pipelines. Useful when an MR depends on another MR being merged first (e.g. waiting for a revert to land before retriggering your MR's pipeline).
Both commands are installed at ~/.local/bin/ and accept either a full MR URL or a plain MR IID.
wait_for_mr_mergePolls a merge request until it reaches merged (exit 0) or closed (exit 1) state.
# Wait using full URL
wait_for_mr_merge https://gitlab.com/gitlab-org/gitlab/-/merge_requests/226808
# Wait using IID + repo flag
wait_for_mr_merge 226808 -R gitlab-org/gitlab
# Custom poll interval (default: 30s)
wait_for_mr_merge 226808 -R gitlab-org/gitlab -i 60
Options:
| Flag | Description |
|---|---|
-R <repo> | Repository in OWNER/REPO format (inferred from URL or current repo) |
-i <seconds> | Poll interval in seconds (default: 30) |
run_mr_pipelineTriggers a new merge request pipeline via the GitLab API (POST /projects/:id/merge_requests/:iid/pipelines).
# Trigger using full URL
run_mr_pipeline https://gitlab.com/gitlab-org/gitlab/-/merge_requests/226128
# Trigger using IID + repo flag
run_mr_pipeline 226128 -R gitlab-org/gitlab
Options:
| Flag | Description |
|---|---|
-R <repo> | Repository in OWNER/REPO format (inferred from URL or current repo) |
Wait for a blocking MR to merge, then immediately trigger a new pipeline for your MR:
wait_for_mr_merge https://gitlab.com/gitlab-org/gitlab/-/merge_requests/226808 && \
run_mr_pipeline https://gitlab.com/gitlab-org/gitlab/-/merge_requests/226128
wait_gdk_mr_mergedZsh function (~/.shellrc/zshrc.d/functions/) that waits for an MR to be merged,
with Home Assistant webhook notifications. Has two modes:
# Poll by MR IID (uses GitLab API)
wait_gdk_mr_merged 226808
# Poll by branch pruning (no argument — watches for the current branch's remote to be pruned)
wait_gdk_mr_merged
Sends waiting_for_mr_merge webhooks to Home Assistant (on while waiting, off when done).
Supports Ctrl-C to abort gracefully.
Note: This is the original GDK-specific version. Prefer wait_for_mr_merge for new usage
as it supports full URLs, configurable intervals, and any GitLab repository.
glab (authenticated via GITLAB_TOKEN)jqcurl (for wait_gdk_mr_merged Home Assistant webhooks)-R&& — wait_for_mr_merge exits 0 on merge, 1 on close, making it safe to chainwait_for_mr_merge and run_mr_pipeline are fully non-interactive and safe for agent userun_mr_pipeline uses glab api to POST; ensure GITLAB_TOKEN has api scopewait_for_mr_merge over wait_gdk_mr_merged — it's more flexible and supports any repoKeep a GitLab issue's native Status in sync with its merge requests, and start implementing an issue by assigning it to the current user and setting the active milestone. Use when asked to start work on an issue, update an issue's status as MRs progress, or track issue state through the dev/review/complete lifecycle.
Run commands in a temporary tmux pane with full interactive zsh environment (login shell, shims, PATH, aliases, TTY).
Hammerspoon macOS automation. Config in ~/.hammerspoon/. Modules: init.lua, spaces, sleepwake, urlrouter, httpserver, meetings, webcam. Keywords: hammerspoon, hs, lua, audiodevice, hotkey, caffeinate, httpserver, Stream Deck, Rectangle Pro, blueutil, AirPods, URL routing, webcam, uhubctl. Use when: editing ~/.hammerspoon/ files, debugging Hammerspoon modules, adding Hammerspoon features, checking Hammerspoon logs.
Use before any Git branch operation in this repo. SSOT for the branch naming convention (<username>/<issue-id>/<branch-name>) — load before creating a branch instead of guessing the name. Also provides helpers for finding a branch's parent, rebasing related branches, force-pushing feature branches, and understanding commit or diff structure across stacked Git branches.
Iteratively test and refine prompts, skills, and agent configurations using opencode run
Inspect GitLab local ClickHouse tables, schemas, ingestion paths, and data patterns. Use for CH table questions, DESCRIBE TABLE, schema/source-of-truth checks under db/click_house, ClickHouse ingestion debugging, and investigating aggregates, distributions, or anomalous data in the GitLab repo.