dotfiles

Use when writing documentation, READMEs, explanations, blog posts, or any prose meant for humans to read

This skill should be used when the user asks to "rebase all open PRs", "update all PRs with latest main", "make sure every open PR is up to date with main", "sync all open PRs onto main", "rebase all my PRs", or wants to bring every open pull request current with its base branch by rebasing in parallel git worktrees, resolving conflicts with a team of agents, and force-pushing.

Groom and prioritize a project backlog — verify each candidate issue's claims against the current codebase, pick the most important N, rewrite them to a ready-to-work standard (Problem/Goals/Decisions/Outcomes/Verification), move them to Ready on the board, and close obsolete issues. Use when asked to "groom the backlog", "triage the backlog", "prioritize issues", "move issues to ready", or "what should we work on next".

This skill should be used when the user asks to "summarize a note", "summarize this article", "replace #summarize-later", "add a summary to a note", "generate takeaways", or mentions summarizing Obsidian notes. Replaces the #summarize-later tag with a high-level summary and actionable takeaways.

This skill should be used when the user asks to "update the changelog", "add changelog entries", "what changed since last release", or when updating CHANGELOG.md with user-facing changes. Follows Keep a Changelog format and filters out internal-only commits.

This skill should be used when the user asks to "improve a prompt", "make this prompt better", "optimize this prompt", "refine this system prompt", or wants to apply concept elevation to compress and clarify LLM instructions.

Use when writing, reviewing, or improving system prompts for AI tools, agents, chatbots, or LLM-powered products. Trigger phrases include "write a system prompt", "create a system prompt", "system prompt for X", "improve this prompt", "review my prompt", "prompt engineering".

How to use the dev CLI and configure dev.yml for any project. Covers all commands, aliases, built-in tasks, dev.yml schema, and common project configurations. Use when helping users set up, configure, or troubleshoot dev CLI usage in their projects.

Socratic coach for breaking down problems to fundamental truths. Use when users want to think through a problem deeply, challenge assumptions, or find innovative solutions. Triggers on requests like "help me think through this", "let's break this down", "what are my blind spots", "I'm stuck on a problem", "challenge my assumptions", or explicit requests for first-principles thinking.

This skill should be used when the user asks to "define a term", "add a definition", "replace `define-later`", "define this note", or mentions defining terms in Obsidian notes. Replaces the `#define-later` tag with a concise definition derived from the note title.

Knows which zsh dotfile to place shell configuration changes into. Use when adding environment variables, aliases, PATH entries, shell options, completions, or any other zsh configuration to the user's dotfiles.

This skill should be used when the user asks to "merge dependabot PRs", "safely merge dependabots", "auto-merge safe dependency updates", "process dependabot PRs", or wants to autonomously analyze and merge Dependabot PRs with comprehensive safety checks.

This skill should be used when the user says "bd go", "go do work", "work on something", "find and do work", or wants the beads agent to autonomously find ready tasks and complete them.

This skill should be used when the user says "bd scan", "scan for issues", "survey the branch", "find deficiencies", or wants to review recent work on the current branch and create beads for any gaps or deficiencies found.

This skill should be used when the user says "learn from that mistake", "remember this for next time", "add that to CLAUDE.md", "don't do that again", or wants to codify a correction or lesson into CLAUDE.md so it persists across sessions.

This skill should be used when the user asks to "rebase dependabot PRs", "rebase dependabots", "refresh stale dependabot branches", or wants to comment "@dependabot rebase" on open Dependabot PRs to trigger a rebase.

This skill should be used when the user says "redo this", "start over", "scrap this approach", "rewrite from scratch", "try a simpler approach", or wants to discard the current implementation and reimplement with an elegant solution using everything learned so far.

This skill should be used when the user asks to "review rails code", "audit rails app", "find over-engineering in rails", "simplify rails services", "review app/services", or wants to analyze a Rails codebase for unnecessary abstractions with actionable refactoring steps.

This skill should be used when the user asks to "review ruby code", "audit ruby codebase", "find over-engineering in ruby", "simplify ruby classes", "review lib/", or wants to analyze Ruby code (libraries, gems, CLI tools) for unnecessary abstractions with actionable refactoring steps.

This skill should be used when the user asks to "audit this repo", "is this safe to run", "security audit", "check this clone", "audit security", "check for vulnerabilities", "scan for malicious code", "analyze security risks", "detect data exfiltration", or mentions security patterns, threat detection, or codebase safety assessment.

This skill should be used when the user asks to "parse JSON", "filter JSON", "transform JSON", "extract fields from JSON", "query JSON data", "format JSON output", "convert JSON to CSV", "reshape JSON", "merge JSON files", or when working with JSON data on the command line. Covers jq filters, built-in functions, and advanced patterns.

Use when working with GitHub PRs, issues, workflows, or CI/CD - automates GitHub operations from terminal

This skill should be used when creating, editing, or debugging Mermaid diagrams. It provides comprehensive syntax references for all 20+ Mermaid diagram types including flowcharts, sequence diagrams, class diagrams, ER diagrams, Gantt charts, and more. Use this skill when users ask for diagrams, visualizations, flowcharts, or any Mermaid-related assistance.

Identify over-engineering in Ruby - prefer simple data structures (Hash, Struct, Data) and pure functions over unnecessary classes