By bendrucker
Automate GitLab workflows using glab CLI: manage merge requests and todos, debug and validate CI/CD pipelines, query REST/GraphQL APIs for issues and jobs, reference documentation, all via conversational commands.
npx claudepluginhub bendrucker/claude --plugin gitlabGitLab 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.
Working with GitLab merge requests via glab. Use when creating, updating, reviewing, or merging MRs.
Managing GitLab todos inbox. Use when listing, filtering, or triaging GitLab todos (mark done, mark pending).
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
Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques
Executes bash commands
Hook triggers when Bash tool is used
Team-oriented workflow plugin with role agents, 27 specialist agents, ECC-inspired commands, layered rules, and hooks skeleton.
Complete collection of battle-tested Claude Code configs from an Anthropic hackathon winner - agents, skills, hooks, rules, and legacy command shims evolved over 10+ months of intensive daily use
Complete collection of battle-tested Claude Code configs agents, skills, hooks, rules, and legacy command shims evolved over 10+ months of intensive daily use
AI-supervised issue tracker for coding workflows. Manage tasks, discover work, and maintain context with simple CLI commands.