From gitlab-skills
Use this skill when the user wants to trigger a new GitLab CI pipeline, run CI, start a build, or kick off a pipeline. Triggers on phrases like "trigger pipeline", "run CI", "start build", "kick off pipeline", "re-run CI", "run the pipeline".
npx claudepluginhub yjhjstz/cc-skills --plugin gitlab-skillsThis skill is limited to using the following tools:
Trigger a new GitLab CI/CD pipeline run.
Verifies tests pass on completed feature branch, presents options to merge locally, create GitHub PR, keep as-is or discard; executes choice and cleans up worktree.
Guides root cause investigation for bugs, test failures, unexpected behavior, performance issues, and build failures before proposing fixes.
Writes implementation plans from specs for multi-step tasks, mapping files and breaking into TDD bite-sized steps before coding.
Trigger a new GitLab CI/CD pipeline run.
Extract the branch name from the user's message if provided. If not specified, default to the current branch.
Use glab CLI. Must run from a git directory with GitLab remote.
Determine branch: If the user specified a branch name, use it. Otherwise use current branch (git branch --show-current).
Confirm with user before triggering: show branch name and ask for confirmation.
Trigger: glab ci run -b <BRANCH>
Show result: Display the new pipeline URL, suggest /gitlab-ci to monitor status.
IMPORTANT: Do NOT use interactive/TUI commands (glab ci view, glab ci trace).