Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From jylhis-skills
Use for GitLab work — CI/CD pipeline configuration in `.gitlab-ci.yml` (pipeline templates, downstream pipelines, Docker builds, caching strategies, CI/CD components, runner config, artifacts vs cache, pipeline inputs, duplicate pipeline traps) and the `glab` CLI for terminal-based GitLab workflows (merge requests, issues, epics, work items, comments, Quick Actions, GitLab API queries, inline review comments). Read the matching reference before editing pipelines or running glab.
How this skill is triggered — by the user, by Claude, or both
Slash command
/jylhis-skills:gitlabThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Pick the topic and read its reference before editing GitLab pipelines
assets/graphql/create-note.graphqlassets/graphql/epic-notes.graphqlassets/graphql/project-work-item.graphqlreferences/cicd.mdreferences/cicd/pipeline-templates.mdreferences/glab.mdreferences/glab/epic-comments.mdreferences/glab/epics.mdreferences/glab/issue-links.mdreferences/glab/nested-groups.mdreferences/glab/work-items.mdscripts/add-inline-comment.shscripts/batch-label-issues.shscripts/ci-debug.shscripts/create-epic-note.shscripts/create-mr-from-issue.shscripts/epic-notes.shscripts/mr-review-workflow.shscripts/post-inline-comment.pyscripts/sync-fork.shPick the topic and read its reference before editing GitLab pipelines or scripting against the GitLab API.
| Topic | When to read | Reference |
|---|---|---|
| CI/CD (.gitlab-ci.yml) | pipeline templates, components, downstream pipelines, Docker builds, caching, runner config, artifacts vs cache, pipeline inputs | references/cicd.md (+ cicd/pipeline-templates.md) |
| glab CLI | merge requests, issues, epics, work items, comments, Quick Actions, GitLab API, inline review comments | references/glab.md (+ glab/work-items.md, glab/issue-links.md, glab/epics.md, glab/epic-comments.md, glab/nested-groups.md) |
Helper scripts live under scripts/ (sibling to references/):
add-inline-comment.sh, batch-label-issues.sh, ci-debug.sh,
create-epic-note.sh, create-mr-from-issue.sh, epic-notes.sh,
mr-review-workflow.sh, post-inline-comment.py, sync-fork.sh.
Assets (GraphQL queries) live under assets/graphql/.
After reading the reference, follow its guidance for the task.
Guides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Synthesizes the current conversation into a structured spec (PRD) and publishes it to the project issue tracker with a ready-for-agent label, without interviewing the user.
npx claudepluginhub jylhis/skills --plugin jylhis-small-business