xdg-claude

Record a durable engineering decision in the repo's append-only decision log (docs/decisions.md by default). Use after choosing between real alternatives — a dependency, a version pin, an architecture or protocol choice, a deliberate non-implementation, or a reversal of an earlier decision. Also use when the user says "log that decision", "write this down", or asks what was decided and why.

Structural code search and refactoring via ast-grep. Reach for this when Edit fails with "old_string not unique", when refactoring across formatting variations, or when matching code shape rather than text.

Outline a file or package (functions, classes, methods, types, imports, exports) instead of reading it whole. Use before opening an unfamiliar or large file to orient, when surveying a package's API surface, or to find where a symbol is defined so you can Read just that range -- any "what's in / list / show me the structure of" need. Not for "where is X used" (search) or "how does X work" (read the body).

How to author Claude Code plugins (agents, skills, commands, hooks, MCP servers) and distribute them via a marketplace. Use when creating, structuring, or revising a plugin, deciding which skill pattern fits, or writing SKILL.md / agent / hook / manifest files.

Implement TODO.md items via isolated subagents, then adversarially verify correctness. Drives a phased loop that implements one checkbox at a time, runs independent lint/test/review subagents, handles human verification, and commits per subsection.

Create and maintain structured TODO.md implementation plans with phased tasks, testing philosophy, and verification checklists. This skill should be used when the user asks to create a TODO file, implementation plan, project roadmap, or phased development plan. Also use when asked to update or extend an existing TODO.md in this style.

When the user asks to be interviewed, grilled, or talked through an under-formed plan, design, or strategy, use this skill to run a structured tree-shaped Q&A persisted to disk. Elicitation only; does not produce the final artifact.

Commit current changes with intelligent analysis and best-practice messages

When the user asks to commit, check in, or save changes, consult this skill to decide whether to delegate to the commit subagent and how to craft the prompt.

Manage Jira issues via the jira-cli tool.

When the user asks what to refactor, where to improve code quality, or for analysis of refactoring opportunities, consult this skill to decide whether to delegate to the plan-refactor subagent and how to craft the prompt.

When the user asks to refactor, restructure, extract, rename, simplify, or clean up code without changing behavior, consult this skill to decide whether to delegate to the refactor subagent and how to craft the prompt.

Analyze code and recommend refactoring opportunities

Improve code quality without changing behavior via surgical refactoring

When a task would pollute the main context with intermediate results, file reads, or speculative exploration, consult this skill to decide whether to delegate to the isolated subagent and how to craft the prompt.

Execute a focused task in isolated context without polluting main conversation history

Analyze code quality, security, performance, and maintainability

When the user asks for a code review, PR review, or critical look at recent changes, consult this skill to decide whether to delegate to the code-review subagent and how to craft the prompt.

Search code and text files via ripgrep (rg) in Bash. Prefer rg over the Grep tool: rg gives full unredacted output, supports pipe composition, and exposes flags Grep does not (-F, -w, -L, -v).

Extract a known field from a YAML file by running yq instead of reading the whole file.

Extract a known field from a JSON file by running jq instead of reading the whole file.