Playbook for monitoring and fixing a CI/CD pipeline (GitHub Actions / GitLab CI). Load this BEFORE running ANY pipeline command or touching a run/job. Triggers (any = load now): running gh run/gh pr checks/glab ci (status/view/trace/list); checking, watching, polling, or waiting on a pipeline/build/checks/run/workflow/job after a push or PR/MR; the build is red/failing and you need the log, the failing job, or to fix it until green; deciding whether a failing check is pre-existing or your regression; a flaky job or re-run decision. Phrases: "check CI", "why is the build failing", "is the pipeline green". Covers the terminal-state poll list, gh/glab recipes for watching runs and fetching failed-job logs, the fix-red-until-green procedure, the forbidden fixes (disable/skip/rerun/[skip ci]/force-push), the pre-existing-failure exception, and the auto-merge caveat. Do NOT load it for opening/promoting a PR/MR (use pr-mr) or for local-only test runs that never touch a pipeline.
EnglishPlaybook for reading and creating GitLab issues, tasks, and work items from the CLI. Load this BEFORE you read an issue/work-item URL, create or update an issue or task, choose between an issue and a task, apply or create labels, set start-date/estimate planning metadata, upload an image to an issue/task description, or write a rich issue/task body (mermaid, tables, templates). It covers glab issue view vs glab api, the work-item URL gotcha, the list→match→create→apply label workflow, glab api --form image uploads, and the bug/feature description templates. Do NOT load it for pull-/merge-request lifecycle work (use pr-mr) — including the PR/MR body checklist sync — or for pipeline monitoring (use ci-cd-monitoring). The "never surface an auth token" guardrail lives in core AGENTS.md and applies regardless.
EnglishIncludes CI CD Monitoring and GitLab Issues.
Supported by the Atlas install prompt. Skill-specific requirements vary.
Pack stats
What’s included
CI CD Monitoring
Playbook for monitoring and fixing a CI/CD pipeline (GitHub Actions / GitLab CI). Load this BEFORE running ANY pipeline command or touching a run/job. Triggers (any = load now): running gh run/gh pr checks/glab ci (status/view/trace/list); checking, watching, polling, or waiting on a pipeline/build/checks/run/workflow/job after a push or PR/MR; the build is red/failing and you need the log, the failing job, or to fix it until green; deciding whether a failing check is pre-existing or your regression; a flaky job or re-run decision. Phrases: "check CI", "why is the build failing", "is the pipeline green". Covers the terminal-state poll list, gh/glab recipes for watching runs and fetching failed-job logs, the fix-red-until-green procedure, the forbidden fixes (disable/skip/rerun/[skip ci]/force-push), the pre-existing-failure exception, and the auto-merge caveat. Do NOT load it for opening/promoting a PR/MR (use pr-mr) or for local-only test runs that never touch a pipeline.
GitLab Issues
Playbook for reading and creating GitLab issues, tasks, and work items from the CLI. Load this BEFORE you read an issue/work-item URL, create or update an issue or task, choose between an issue and a task, apply or create labels, set start-date/estimate planning metadata, upload an image to an issue/task description, or write a rich issue/task body (mermaid, tables, templates). It covers glab issue view vs glab api, the work-item URL gotcha, the list→match→create→apply label workflow, glab api --form image uploads, and the bug/feature description templates. Do NOT load it for pull-/merge-request lifecycle work (use pr-mr) — including the PR/MR body checklist sync — or for pipeline monitoring (use ci-cd-monitoring). The "never surface an auth token" guardrail lives in core AGENTS.md and applies regardless.
Quick start
- Choose your skills. Select individual skills above, or choose the entire pack.
- Copy the install prompt. Use Copy install prompt above the list.
- Send it to your agent. Paste into your coding agent’s chat. Your agent reviews the source and guides the setup.
Try it with your agent
After installation, start with a request like:
Use the CI CD Monitoring skill to help with my task.
Ask me for the context you need before getting started.Requirements & license
- A coding agent that can access your project files and install skills.
- Your agent checks each skill’s instructions, dependencies, and permissions during setup.
- License details are not provided in these listings. Check the author’s terms before using the skills.