.dotfiles

Coordinate parallel ticket workers as an event-driven control plane through repos worktrees, Pi sessions, delegated pull-request review, squash merges, and filesystem tracker frontiers. Use when orchestrating implementation tickets rather than implementing or reviewing one ticket directly.

Implement one ticket handed off by the orchestrator and open a PR for review.

Manage work in the local Tickets filesystem tracker. Use when the user asks to inspect, search, create, claim, update, move, rename, complete, or lint a Tickets project or ticket.

Plan a huge chunk of work — more than one agent session can hold — as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.

Provides comprehensive code review guidance. Helps catch bugs, improve code quality, and give constructive feedback. Use when: reviewing pull requests, conducting PR reviews, code review, reviewing code changes, establishing review standards, mentoring developers, architecture reviews, security audits, checking code quality, finding bugs, giving feedback on code.

Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

Use Datadog's MCP server through mcp2cli for agent-native Datadog investigation workflows: DDSQL, Kubernetes resource inspection, metric context/tag discovery, span/log/RUM attribute discovery and aggregation, monitor authoring/validation, dashboard widgets, notebooks, incidents, services, dependencies, and error tracking. Prefer pup-datadog-cli for stable scriptable Datadog API queries.

Route Datadog observability tasks between pup-datadog-cli and datadog-mcp. Use this first when the user asks about Datadog and it is not obvious whether the stable pup CLI or the Datadog MCP discovery/enrichment layer is the right tool.

Turn a loose idea into a sequenced map of investigation tickets, then drive them to resolution one at a time.

Generate multiple radically different interface designs for a module. Use when user wants to design an API, explore interface options, compare module shapes, or mentions "design it twice".

Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

Turn any MCP server, OpenAPI spec, or GraphQL endpoint into a CLI. Use this skill when the user wants to interact with an MCP server, OpenAPI/REST API, or GraphQL API via command line, discover available tools/endpoints, call API operations, or generate a new skill from an API. Triggers include "mcp2cli", "call this MCP server", "use this API", "list tools from", "create a skill for this API", "graphql", or any task involving MCP tool invocation, OpenAPI endpoint calls, or GraphQL queries without writing code.

Build a throwaway prototype to flesh out a design — a runnable terminal app for state/business-logic questions, or several radically different UI variations toggleable from one route.

Write a typed call-stack architecture handoff.

Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices.

Turn the current conversation into a PRD and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.

Move issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.

Go from a Jira ticket (usually the current branch name) to a shared understanding of what to build, before any implementation.

Enforces `repos` for worktrees and rebases. Use when creating, resuming, or switching to a worktree, stacking a branch, rebasing or updating a branch onto its base or parent, or resolving, continuing, or aborting a rebase.

Create pull requests. Use when opening a GitHub PR, drafting a PR title/body, preparing a pull request description, or reviewing a branch before PR creation.

Guide for creating, configuring, and distributing Claude Code plugins with hooks, skills, commands, and MCP servers. Use when user asks to create a plugin, set up hooks, add plugin functionality, create a marketplace, or distribute custom Claude Code extensions.

Simplify and refine code for clarity, consistency, and maintainability while preserving all functionality. Focuses on recently modified code.

Use pup for stable, scriptable Datadog API-shaped work: metrics, logs, monitors, dashboards, SLOs, RUM, APM, traces, notebooks, and repeatable shell/runbook commands. Prefer datadog-mcp for discovery, enrichment, DDSQL, Kubernetes resources, monitor validation/recommendations, widgets, incidents, and error tracking.

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.

Reads Confluence Cloud pages through Atlassian CLI (`acli`) and extracts useful page text/metadata. Use when the user asks to read, inspect, summarize, or use a Confluence/wiki page via acli, especially URLs from `*.atlassian.net/wiki/spaces/.../pages/<pageId>/...`.

Reads and lightly updates Jira Cloud work items through Atlassian CLI (`acli`), including metadata, ADF descriptions, comments, attachments, and adding reference links as comments. Use when the user asks to read, inspect, summarize, triage, comment on, or update a Jira issue/work item via acli, especially keys like `FCC-114`.