GitLab REST and GraphQL API access via glab. Use when making API requests, querying project data, or automating GitLab operations.
Executes GitLab API operations via glab commands for automating CI/CD, issues, and repository management.
npx claudepluginhub bendrucker/claudeThis skill inherits all available tools. When active, it can use any tool Claude has access to.
REST and GraphQL API access via glab api.
Auto-resolve to current project values:
:fullpath - Full project path (e.g., group/project):id - Project ID:branch - Current branch:user / :username - Current userglab api projects/:fullpath/merge_requests
glab api projects/:id/issues # GET
glab api projects/:id/issues -X POST -f title="..." # POST with field
glab api projects/:id/issues --paginate # All pages
Pagination pitfall: --paginate concatenates JSON arrays across pages as ][, producing invalid JSON (e.g., [{...}][{...}]). Fix by replacing ][ with , before parsing: .replace(/\]\s*\[/g, ",").
glab api graphql -f query='{ currentUser { username } }'
For pagination, accept $endCursor variable and fetch pageInfo { hasNextPage, endCursor }.
--output json (default) - Pretty-printed JSON--output ndjson - Newline-delimited, works with jq streaming/api/ in GitLab docs/api/graphql/reference/You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.