gitlabhq

@gitlabhq source repo

19 skills
0 followers
9 hours ago last updated

▌
Oak Component Integration 2 · gitlabhq
Integrating a new advanced component with OAK (Omnibus Adjacent Kubernetes). Use this skill when a task involves adding NGINX reverse proxy configuration, Helm values generation, component database documentation, CI jobs, or operator documentation for a new OAK component in omnibus-gitlab.

0
installs
▌
Glab Stack · gitlabhq
Manage stacked diffs and merge requests with the GitLab CLI. Use when the user wants to create, save, amend, sync, navigate, or reorder a stack of dependent merge requests. Triggers on tasks involving stacked diffs, stacked MRs, dependent merge requests, or incremental code review workflows using `glab stack`.

0
installs
▌
Oak Component Integration · gitlabhq
Integrating a new advanced component with OAK (Omnibus Adjacent Kubernetes). Use this skill when a task involves adding NGINX reverse proxy configuration, Helm values generation, component database documentation, CI jobs, or operator documentation for a new OAK component in omnibus-gitlab.

0
installs
▌
Orbit · gitlabhq bundle
Use the `glab orbit` CLI for questions about code structure, blast radius, cross-project links, and relationships across GitLab entities, and to build a repo map. It works on hosted or local data. Skip it for single-entity lookups or writes that `glab` already handles.

0
installs
▌
Orbit CLI · gitlabhq bundle
Index and query a LOCAL checkout of a repository offline with the Orbit CLI (the `orbit` binary, run directly or via `glab orbit`). It builds a DuckDB property graph from the working tree. Use grep for definitions and relationships, context for source bodies, and read-only SQL for aggregations. Use when the request targets the current checkout, working tree, or a branch that is not pushed/indexed remotely, or is explicitly offline/local: index this repo locally, who calls X in my checkout, list definitions in a file, generate a repo map of a local checkout, run SQL over the local code graph, or serve the local graph over MCP. For queries against already-indexed production data in GitLab (a project such as gitlab-org/gitlab, cross-project blast radius, contributor or merge-request aggregation) use the `orbit` skill; for single-entity GitLab lookups or write operations use `glab`.

0
installs
▌
Pajamas · gitlabhq bundle
GitLab Pajamas Design System expert for building UIs with Pajamas components and patterns. Use when: (1) implementing UI that should follow GitLab's Pajamas design system, (2) selecting or configuring Pajamas/GlComponent components (GlButton, GlAlert, GlModal, etc.), (3) translating Figma designs into Pajamas-compliant code, (4) questions about Pajamas component usage, variants, categories, or accessibility, (5) building GitLab-style interfaces, or (6) the user mentions "Pajamas", "GitLab UI", "Gl components", or "design system" in a GitLab context. Works hand-in-hand with the implement-design skill and Figma MCP tools.

0
installs
▌
Ast Grep · gitlabhq
AST-based code search and rewrite via tree-sitter patterns. Use instead of Grep/Edit when a change spans many sites or must respect code structure: structural matching, multi-file batch rewrites, or context-aware queries (e.g. "unwrap inside impl blocks"). Not for a single-file or single-symbol rename — use Edit for that.

0
installs
▌
Update Docs · gitlabhq
Audit and update documentation after code changes. Use when architecture, APIs, or behavior changed and docs may have drifted.

0
installs
▌
Code History · gitlabhq
Investigate the history, usage, and liveness of code using search and git blame/log. Use when determining if code is dead, understanding why something exists, finding all callers before refactoring, or deciding whether something is safe to remove. Also useful for answering "who added this and why" or "is anything still using this".

0
installs
▌
Dataflow Mapping · gitlabhq
Trace and document how data transforms through a multi-step pipeline or function chain, showing intermediate state at each step with concrete example values. Use when explaining a data pipeline or complicated codepaths, tracing how a value changes across function calls, answering questions like "how does X get to Y", or producing a step-by-step dataflow walkthrough for a code review or design doc.

0
installs
▌
Remove LLM Comments · gitlabhq
Remove and tighten unnecessary LLM-generated comments — including narration disguised as "why", restated constraints, and why-comments a named symbol or the code structure already conveys. Use while editing, and as the final narration-comment pass before opening an MR or pushing, to strip the LLM narration the model left behind.

0
installs
▌
Related Repositories · gitlabhq
Registry of related repositories (Siphon, Rails, and other consumed repos) with their git URLs and local checkout paths. Use when you need to find where a related repo is checked out locally, get its git URL, or clone it if it is missing.

0
installs
▌
Debug Clickhouse Queries · gitlabhq
Investigate query evaluation failures in the Knowledge Graph synthetic data pipeline. Use when queries fail or return unexpected results after running the evaluate binary.

0
installs
▌
Clickhouse Query Profiling · gitlabhq
Profile GKG queries against ClickHouse with the query-profiler CLI. For optimizing query performance, comparing query plans, investigating slow queries, or checking ClickHouse resource usage.

0
installs
▌
Glab · gitlabhq bundle
GitLab workflow automation using the glab CLI. Use when the user asks to create, update, close, label, or comment on a GitLab issue, merge request, work item, or epic; to post a note, review comment, or discussion reply; to call the GitLab REST or GraphQL API through "glab api"; to inspect or retry pipelines and jobs; or to configure glab auth against gitlab.com, a self-managed instance, or a local GDK. Read it before any glab write operation, because several field flags fail silently - they exit 0 while posting the wrong content.

1
install
▌
Split Mr · gitlabhq
Analyze the changes on the current branch — both uncommitted work and commits already made (e.g. a PoC or existing MR) — and reason about whether they should be split into smaller, more focused MRs. Identifies natural boundaries (backend/frontend, model/spec, feature/refactor) and proposes a split plan or confirms the changes are cohesive enough to keep as one.

1
install
▌
Gitlab MCP Tool Builder · gitlabhq bundle
Build a new GraphQL-backed MCP server tool in gitlab-org/gitlab. Use when adding or scaffolding a GitLab Duo Agent Platform MCP tool that follows the app/services/mcp/tools/ *Tool + Graphql*Service pattern — covers GraphQL API discovery, the two-class-plus-registration build recipe, and gotchas. Keywords: MCP tool, MCP server, GraphQL tool, GitLab Duo Agent Platform.

1
install
▌
Gitlab Coding Principles · gitlabhq
MUST USE before planning, implementing, refactoring, OR reviewing any GitLab code changes (including merge request reviews, code review feedback, new features, bug fixes). Evaluate every principle group to ensure cross-domain coverage. Triggers: review, reviewing, plan, planning, implement, implementing, refactor, refactoring, MR review, code review.

1
install
▌
AI Principles Review Feedback · gitlabhq
Act on automated review feedback left on the weekly AI principles distillation sync merge requests. Use when asked to address, respond to, or work through Duo review comments on `docs-sync/principles-*` branches, or on merge requests titled "Update AI development principles from SSOT". Classifies each finding, verifies it against the SSOT documentation, applies fixes on the sync branch, drafts replies, and escalates distiller defects.

1
install

19 published skills