bendrucker
UserMy personal plugin marketplace and settings for Claude Code
Categories
Indexed Skills (39)
claude-codeskill
Creating and optimizing Claude Code Skills including activation patterns, content structure, and development workflows. Use when creating new skills, converting memory files to skills, debugging skill activation, or understanding skill architecture and best practices.
commentsaudit
Audit code comments for AI slop: restatement, narration/decision-log, self-praise, docstring-scope, and section-divider banners. Audits a diff (the comments a change introduced) or a whole repo, ranks by intrinsic complexity, fans out judging agents, and applies the trims to a fresh branch. Use when reviewing a branch or merge request, or sweeping a slop-heavy codebase.
gitconflicts
Resolving git merge conflicts during rebase, merge, or cherry-pick. Use when conflicts arise. Can also drive the operation to completion and push when asked (e.g. "fix conflicts and push").
githubactions-monitor
Monitor GitHub Actions runs and extract failure diagnostics. Use when watching PR CI, branch builds, or specific workflow runs.
gitlabci-monitor
Watch GitLab CI and investigate pipeline failures. Use when a pipeline or job is failing or red, when watching MR CI, branch builds, or a specific pipeline, when waiting for CI to go green, or when authoring or validating .gitlab-ci.yml.
image
Generate a meme by overlaying text on an image. Use when asked to make a meme, caption an image, add meme text, or produce classic Impact macros, TV-subtitle stills, white-bar captions, or multi-label formats (Drake, distracted boyfriend, whiteboard).
pull-requestbabysit
Monitor a PR's CI, fix trivial failures, and self-cancel when green; --merge drives to merged, --reviews hands off to AI-review triage.
agent-ideas
Harvest agent-tooling ideas from prominent developers.
activitywatchactivity
Report real device usage from ActivityWatch. Covers per-app time, window titles, and active vs idle spans. Use when asked "what apps did I use", "how long was I in X", "what did I work on today", "how much was I active vs idle", or to mine usage patterns for automation.
atuinhistory
Report shell history from atuin's local capture. Covers what commands ran, when, where, and how they exited. Use when asked "what commands did I run", "what was I working on in the terminal", "have I ever run X", "how do I usually invoke X", or about recent shell activity, command frequency, or failed commands.
claude-codeagent-team
Orchestrating Claude Code agent teams. Use when creating teams, spawning teammates, assigning tasks, configuring teammate modes, or setting up team quality gate hooks.
claude-codehandoff
Hand the current conversation off to a fresh background agent that picks up the work immediately, so you can step away and track it independently. Use when the user wants to background the current work, keep going without them, continue in a separate session, or says "hand this off", "run this in the background", "keep working on this while I'm gone", or "spin up an agent to finish this".
claude-codehook
Configure, create, or troubleshoot Claude Code hooks (PreToolUse, PostToolUse, UserPromptSubmit), debug hook failures, or set up any automation within Claude Code. Examples include "I want to run tests before every file edit", "My hook isn't firing", "1 out of 2 hooks ran", or "How do I create a hook that formats JSON output with jq?"
claude-codesession
Query Claude Code session history via a DuckDB index over `~/.claude/projects/`. Use when asked about Claude Code activity ("how many tokens today?", "what did I work on this week?") or instead of reading, grepping, or jq-ing session transcripts. Not for codebase search, git log queries, or arbitrary databases.
githubpr-comments
Fetch, reply to, and resolve review threads on a GitHub pull request. Use when checking what review feedback needs addressing, whether threads are resolved, replying to review comments, or clearing AI-reviewer threads after acting on them.
gitlabmerge-request
Working with GitLab merge requests via glab. Use when creating, updating, reviewing, or merging MRs, enabling auto-merge or merge trains, requesting or re-requesting reviewers, handling approvals, or working review threads, discussions, and draft notes. Load before running any `glab mr` or MR-mutating `glab api` command.
issuerefine
Refining issues with technical context and structured details. Use when expanding a brief bug, feature, or refactor description into a detailed issue suitable for developers and AI agents.
linear
Interacting with Linear issues, projects, and teams. Use when creating issues, updating issues, querying issues, managing projects, working on tasks, discussing backlogs, or any interaction with Linear.
planreview
Review how an implementation diverged from its approved plan. Forks a clean-context agent over the plan and the diff to surface requirements drift and warranted follow-ups. Use at finish time or before opening a PR.
pull-requestcreate
Create a pull request, merge request, or change request with proper formatting and content guidelines. Invoke when the user wants to create, open, or submit a PR, MR, or CR—including after committing changes.
pull-requestfollow-up
Follow up as the author on review feedback left on your own PR/MR: check which reviewer comments still need a response, investigate how threads were resolved (including silent resolves), and draft replies. With --auto, autonomously triage AI-reviewer (bot) threads and loop until the reviewer is satisfied, clearing a bot review hands-off. With --local, run the same bot loop pre-push through the reviewer's CLI (Greptile, CodeRabbit) against unmerged commits, before any PR exists. Use when reviewers commented on your PR and you need to respond or satisfy them. Use --local proactively, without being asked, whenever you are about to push or open a PR in a repo with a supported bot (bot config present, CLI installed). Triggers: "respond to review comments on my PR", "address reviewer feedback", "make the bot reviewer pass", "greptile review", "coderabbit review", "run the review bot locally", "bot review before pushing".
raycast
Raycast extension development. Use when working with @raycast/api imports, Raycast commands/tools, or building extensions.
researchprior-art
Research existing solutions when exploring a new problem space. Use when the user mentions "prior art", "existing solutions", "what libraries exist for", or wants to understand the landscape before building.
reviewcode
Review the current diff for correctness bugs and reuse/simplification/efficiency cleanups at a given effort level. Use for "review my changes", "review the diff", "find bugs in my changes", or as the correctness pass before opening a PR. Low/medium surface fewer, high-confidence findings; high through max broaden coverage and may include uncertain findings. Pass --fix to apply the findings to the working tree after the review.
reviewfollow-up
Follow up as the reviewer on a PR/MR you reviewed: did the author's fixes actually grasp each concern you raised, or just go through the motions? Finds silently resolved or mechanically-fixed threads and returns a graded re-review call. Use when you left review comments and want to verify the author acted on them before re-approving. Triggers: "did they fix my review comments", "re-review this PR", "check whether the author addressed my feedback".
macjxa-run
Execute JXA scripts scoped to a macOS application. Use when running JXA expressions or script files against an app via osascript. Validates Application() scope via AST.
coverage
Measure Bun test coverage and close gaps on a specific file. Use when adding or editing tests, when asked about coverage, or when the PostToolUse coverage hook reports uncovered lines.
interviewclarify
Targeted interview for execution-time clarification. Use when you hit an ambiguity or decision point during implementation that needs user input before proceeding.
mermaid
Create and validate Mermaid diagrams. Use when creating, editing, or reviewing Mermaid diagrams in markdown files.
opentelemetry
OpenTelemetry instrumentation conventions. Use when instrumenting code with spans, setting up tracing, or writing trace tests.
pull-requestupdate
Update a pull request or merge request body to reflect the current state of changes. Use when a PR/MR has evolved through additional commits and the body needs to reflect what will be merged.
cleye
Type-safe CLI argument parsing with cleye, the standard parser for this repo's Bun scripts. Use when writing or editing any script that takes arguments (flags, positional parameters, subcommands, --help) instead of reading existing scripts for the pattern.
gitlabapi
GitLab REST and GraphQL API access via glab. Use when making API requests, running GraphQL queries or mutations, querying project data, automating GitLab operations, or looking up GitLab feature, API, or CI/CD documentation.
issue
Implement a feature or fix based on an issue. Use when given an issue URL to work on, or when implementing changes described in a tracked issue. Supports GitHub, Linear, and GitLab.
bun
Bun runtime patterns. Use when running bun commands, working with package.json/bun.lock, writing TypeScript scripts under Bun, or developing Claude Code plugins.
interviewplan
Comprehensive interview for planning new features or changes. Use when the user wants thorough upfront planning before implementation, or when starting work on a complex feature.
macjxa
Writing JXA (JavaScript for Automation) code for macOS automation. Use when authoring JXA scripts, learning JXA syntax, or understanding how to automate macOS apps via Application() calls.
Reading and managing Apple Mail via JXA. Use when working with email, archiving messages, or processing the inbox.
prefer-headers
Fixture exercising the prefer-headers rule across its boundary cases.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.