By bendrucker
Manage GitLab workflows entirely from the terminal using the glab CLI — query issues and merge requests, debug CI/CD pipelines, validate pipeline configs, navigate GitLab docs, and handle todos without leaving your editor.
GitLab REST and GraphQL API access via glab. Use when making API requests, querying project data, or automating GitLab operations.
Investigate GitLab CI pipeline failures and extract diagnostic information. Use when checking pipeline status, debugging failed jobs, or monitoring CI after a push. Identifies failing jobs, extracts relevant error output, and returns a concise summary.
Working with GitLab CI/CD pipelines and jobs. Use when viewing pipelines, debugging jobs, or validating CI configuration.
Browsing GitLab documentation efficiently. Use when you need to look up GitLab features, configuration, API details, or CI/CD syntax.
glab CLI basics and GitLab workflow overview. Use when working with GitLab repositories or adapting GitHub patterns to GitLab.
Executes bash commands
Hook triggers when Bash tool is used
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
My personal plugin marketplace for Claude Code, Anthropic's AI coding assistant.
This repository provides plugins for Claude Code, organized as a plugin marketplace. Plugins extend Claude Code with language conventions, workflow automation, service integrations, and custom behaviors.
It also contains my user configuration.
Many plugins include TypeScript hooks and scripts that require Bun to run. See Bun's installation guide for setup instructions. Bun runs TypeScript natively and auto-installs missing dependencies on first run.
Browse the plugins/ directory to see available plugins. Each plugin has its own README describing its contents.
The user/ directory contains user-level Claude Code configuration that gets symlinked to ~/.claude. This includes global instructions, settings (plugins, permissions, sandbox), and hooks that apply across all projects.
To test a plugin locally without publishing:
claude --plugin-dir ./plugins/<name> --setting-sources local
This isolates the session from user/project settings, loading only the specified plugin. Use this to verify changes before committing.
MIT © Ben Drucker
npx claudepluginhub bendrucker/claude --plugin gitlabWriting style enforcement hooks and AI trope detection
Managing Linear issues, projects, and teams
Code review workflows for peer and self review
Cross-tool daily review workflow
POSIX-compliant trailing newline management for files
GitLab CLI (glab) expertise for managing merge requests, issues, CI/CD pipelines, and repositories from the command line
GitLab DevOps platform integration. Manage repositories, merge requests, CI/CD pipelines, issues, and wikis. Full access to GitLab's comprehensive DevOps lifecycle tools.
Git and PR workflows with code review, onboarding, and PR enhancement
The model must apply when tasks involve .gitlab-ci.yml configuration, GitLab Flavored Markdown (GLFM) syntax, gitlab-ci-local testing, CI/CD pipeline optimization, GitLab CI Steps composition, Docker-in-Docker workflows, or GitLab documentation creation. Triggers include modifying pipelines, writing GitLab README/Wiki content, debugging CI jobs locally, implementing caching strategies, or configuring release workflows.
GitLab workflow — MR, issue, and merge skills using glab CLI
GitHub workflow, Actions monitoring, and rulesets management