gitlab
Skill1 starsChanged 3 months agoMITView on GitHub
Operate GitLab from the terminal with `glab`: inspect or update merge requests, issues, pipelines, jobs, and releases; create or debug `.gitlab-ci.yml`; and improve variables, rules, caches, artifacts, and CI performance. Use for requests such as "check this MR" or "why did the pipeline fail". Do not use for GitHub or deep Kubernetes-agent work.
14 other projects use a version of this.
Adopted by
Most recently taken up by
- stijnvanhulle/agentstheir own version, first seen Nov 1, 2026
- SHYXIN/skillstheir own version, first seen Nov 1, 2026
- G1Joshi/Agent-Skillstheir own version, first seen Oct 13, 2026
- microsoft/hve-coretheir own version, first seen Oct 13, 2026
- OpenHands/extensionstheir own version, first seen Oct 8, 2026
- odyssey4me/agent-skillstheir own version, first seen Oct 6, 2026
Used with
Projects with it also use linear.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
OpenAISkilllinear
Manage issues, projects & team workflows in Linear. Use when the user wants to read, create or updates tickets in Linear.
Also in 3 projects that use this
Other versions14 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 14
- microsoft/hve-core★ 1.6ksame name
- refly-ai/refly-skills★ 204same name
- OpenHands/extensions★ 167same name
- AceDataCloud/Skills★ 17same name
- G1Joshi/Agent-Skills★ 15same name
- odyssey4me/agent-skills★ 13same name
- koderover/devops-skills★ 7same name
- SHYXIN/skills★ 6same name
- apideck-libraries/api-skills★ 4same name
- fworks-tech/agenthood★ 3same name
4 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository14 other files it gives its agents.
- audit-pi-sessionSkill
- bash-scriptSkill
- cli-uxSkill
- code-quality-gateSkill
- docs-pesapSkill
- external-reviewSkill
- githubSkill
- good-apiSkill
- prekSkill
- pythonSkill
- rust-pesapSkill
- tdd-pesapSkill
- torcSkill
- uvSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.
0
Common
Most of the 10 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 29
Read the matching reference and inspect repository guidance or CI files that govern the target.
- Very specific: line 35
Verify with follow-up glab inspection or a pipeline rerun when appropriate.
“Common” is measured: kept by at least 6 in 10 of the 10 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
GitLab
Resolve the project and target first, then gather remote evidence with glab
before proposing or making changes.
Task router
Open only the reference whose trigger matches the task:
- GitLab commands — authentication, merge requests, issues, releases, repository operations, environment, and mutation safety.
- Pipelines — run and job triage,
.gitlab-ci.yml,rules,needs, cache, artifacts, matrices, and CI performance.
Core workflow
- Confirm project/group, MR/issue/pipeline/release target, and desired outcome.
- Read the matching reference and inspect repository guidance or CI files that govern the target.
- Gather current state with
glablist, view, status, or API output. - Diagnose from concrete MR state, discussion threads, jobs, logs, artifacts, variables, rules, or pipeline configuration.
- Apply the smallest reliable action or configuration change.
- Verify with follow-up
glabinspection or a pipeline rerun when appropriate; do not infer success from a mutation command alone.
Output
Report key glab evidence, findings or actions, pipeline/configuration changes,
verification status, and remaining risks or next steps.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.