Claude Skills by bendrucker

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.

Follow up on review feedback you received on a PR/MR: check resolution state, find silent resolves, draft replies. Use when checking what review comments need responses, investigating how threads were resolved, or drafting follow-up replies.

Triage and batch-implement Claude-tagged Things todos as PRs for the claude config repo. Use when the user wants to work on their Claude Code improvement backlog, process Things todos tagged claude-code, or batch-implement configuration changes.

Raycast extension development. Use when working with @raycast/api imports, Raycast commands/tools, or building extensions.

Find deepening opportunities in a codebase. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.

Live tmux dashboard for reviewing inbound pull requests across GitHub and GitLab. Use when reviewing multiple PRs, checking review queue, batch reviews, or managing a review dashboard.

Terraform Cloud workspace management, run monitoring, and log retrieval. Use when listing workspaces, checking run status, fetching plan/apply logs, or looking up providers and modules in the Terraform Registry.

Triage and prioritize the Things Today list. Use when the user wants to review, prioritize, or reorder their Today list.

Tmux session, window, and pane management. Use when capturing output, sending keys, opening processes in panes, or checking notifications.

Enforce direct, concise prose style and catch writing slop. Use when writing or editing PR descriptions, issue bodies, commit messages, documentation, Slack messages, or any human-facing text. Also use when asked to clean up, rewrite, or "de-AI" existing text.

Review Claude Code release notes for changes relevant to the user's skills, plugins, and tool usage. Use when the user asks "what's new in Claude Code?", "check for updates", "release notes", "new features", "what changed recently?", or wants to stay current with Claude Code.

GitHub Actions CI/CD workflow development and run monitoring. Use when creating or editing .github/workflows YAML files, configuring triggers, jobs, matrix strategies, caching, or artifacts. Also covers gh CLI for monitoring runs, viewing logs, and debugging failures.

Managing GitLab todos inbox. Use when listing, filtering, or triaging GitLab todos (mark done, mark pending).

Monitor a PR's CI, fix trivial failures (lint, types, formatting), and self-cancel when green. Use after pushing when you want hands-off CI monitoring with automatic fixes.

Bun runtime patterns and best practices. Use when running scripts with bun, using bunx, writing Bun shell scripts, managing bun.lock, or running bun test.

Reading and managing macOS Calendar events. Use when checking schedules, finding events, creating meetings, or answering questions about availability.

Use this skill when you need to configure, create, or troubleshoot Claude Code hooks. This includes setting up PreToolUse hooks, PostToolUse hooks, UserPromptSubmit hooks, debugging hook failures, or 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?"

View current session info or search conversation history. Use when debugging sessions, reviewing activity, finding past discussions, or summarizing recent work.

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.

Branch workflow automation with git-town. Use when creating feature branches, syncing with upstream, proposing PRs, or managing stacked branch workflows.

Resolving git merge conflicts. Use when rebasing, merging, or cherry-picking results in conflicts.

Git workflow and branching best practices. Use when working with git commands, creating branches, or pushing changes.

Managing GitHub notifications inbox. Use when listing, filtering, or triaging notifications (mark read, done, unsubscribe).

Fetch unresolved review comments from a GitHub pull request. Use when checking what review feedback needs to be addressed, whether review comments have been resolved, or resuming work on a PR with outstanding feedback.

GitLab REST and GraphQL API access via glab. Use when making API requests, querying project data, or automating GitLab operations.

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.

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.

Targeted interview for execution-time clarification. Use when you hit an ambiguity or decision point during implementation that needs user input before proceeding.

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.

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.

Create and validate Mermaid diagrams. Use when creating, editing, or reviewing Mermaid diagrams in markdown files.

Batch-process multiple issues into draft PRs using parallel worktrees. Use when implementing several related issues simultaneously, creating multiple PRs in parallel, or batch-processing a backlog.

Interactive daily review workflow across Calendar, Things, GitHub, and Linear. Use when the user asks for a daily review, morning review, evening review, or weekly review.

Detailed planning guidelines and best practices. Use when you want explicit guidance on creating high-quality implementation plans, or when a plan was rejected and you need to understand why.

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.

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.

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.

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.

Review a pull request when requested by a peer. Use when reviewing PRs, providing code review feedback, or analyzing proposed changes. Supports GitHub and GitLab.

Self-review your own code changes using a visual diff viewer. Opens a GitHub-style web UI where you can add comments on changed lines. Comments are returned to Claude for action.

Running and managing Apple Shortcuts via the macOS shortcuts CLI. Use when the user wants to run, list, or inspect shortcuts.

Creating Apple Shortcuts programmatically as plist XML files. Use when the user wants to build, generate, or author Apple Shortcuts without the GUI app.

Quick captures to the Things 3 inbox. Not for reads (things:jxa), scheduled tasks, updates, or projects (things:url).

Read and query Things 3 data (lists, todos, projects, tags, logbook). Not for writes — use things:url to create/update, things:inbox for quick captures.

Create, update, and manage Things 3 tasks and projects. Not for reads — use things:jxa to query data. For simple inbox captures, use things:inbox.

Fixes type ignores in a file, directory, or codebase by discovering ignores and dispatching parallel fixer agents. Use when cleaning up type ignores across multiple files, eliminating ignores before a release, or batch-fixing type errors.

Create wireframes for UI mockups. Supports SVG (precise layouts) and HTML/Tailwind (standard UI patterns). Use when creating wireframes, mockups, or skeletal UI layouts.