dots

Safely add a directory to Claude Code's Bash tool PATH. Use when a binary runs in your terminal but is "command not found" inside Claude Code's Bash tool, when adding a directory to PATH for Claude Code, when configuring CLAUDE_ENV_FILE, or when settings.json env.PATH did not work. Explains why env.PATH replaces rather than appends PATH and is not variable-expanded, why ~/.zshrc PATH exports are dropped, and the supported SessionStart hook fix.

Create or improve a Claude Code skill/slash command with best practices for structure, dynamic context, and safety. Use for creating new skills, improving existing ones, or learning skill authoring.

Launch a dynamic Workflow where the top-tier session model (Fable, or Opus when Fable is unavailable) handles planning and orchestration while implementation subagents run on Sonnet for routine tasks and Opus for complex ones. Use when the user wants to orchestrate a build, a dynamic workflow, a model-tiered build, fable or opus planning with sonnet and opus implementation, or tiered agents.

Open a PR, wait for CI to pass, fix failures, address review comments, and loop until fully green. Use when opening a PR, fixing CI, or addressing review feedback.

Manage recurring tasks in the local Argus daemon via its HTTP API. Use when the user wants to schedule a task locally in argus, create a cron-driven task, fire X every weekday/hour/morning, set up a recurring agent that needs local filesystem access (logs in ~/.argus, local databases, dotfiles), list or update existing argus schedules, or run an argus schedule now. Distinct from /schedule, which creates remote cloud routines without local access.

Generate a handoff prompt to pass context to another agent thread. Use when switching repos, handing off work, or sharing context between agents.

Merge current branch to the default branch via GitHub PR merge. Use when ready to merge a PR or land a branch.

Generate SVG logo alternatives with side-by-side comparison. Use when creating logos, branding, or project icons.

Render a Markdown file to GitHub-flavored HTML and open a styled local preview (light + dark) in the browser. Use when the user wants to preview markdown, see how a README renders on GitHub, check that relative screenshots or images display correctly, or get a GitHub-like local preview without installing grip or glow.

Mark the current Argus task as complete. Use when the work for the current worktree is done and the user wants the task to transition to the "complete" status.

Build a self-contained, single-file HTML presentation deck from talking points or a source doc, using a terminal/TUI-styled template with keyboard, tap, and swipe navigation. Use when the user wants to create slides, build a presentation or deck, turn talking points or a doc into a talk, make an HTML slideshow, or produce a presentation as a shareable artifact (instead of Google Slides).

Scheduled KB maintenance — ingest yesterday's meetings + session captures, synthesize raw notes into existing topical docs (decisions, people changes, conventions), resolve conflicts, age out stale entries, fix frontmatter and links. Translates raw data into knowledge. Runs unattended; never asks for confirmation. Use for KB maintenance, knowledge base cleanup, dream consolidation, memory hygiene, or as a scheduled daily KB pass.

Read text aloud using text-to-speech. Use when the user says "speak to me", "read to me", "read this aloud", "say this", "speak the summary", or asks to hear something spoken.

Re-review with fresh eyes. Zero regressions. Go slow and analyze everything. Use for a paranoid final review before merging.

Code review panel for current branch changes. Use for reviewing PR changes, code review, or getting feedback on branch changes.

Full ship pipeline: /review + fix + /improve + fix + /merge in one command. Use when ready to ship a branch end-to-end.

Walk every unresolved review thread on a PR, triage each one, reply with a rationale of whether or not the comment will be acted upon, make the code change if warranted, and mark the thread resolved. Use when the user asks to address only the open PR comments without re-running CI, respond to review feedback, resolve review threads, or clear bot comments on a PR.

Orchestrate a stack of dependent Argus tasks that produce a chain of stacked PRs. Use when the user has a multi-milestone plan that should land as N PRs where each branches off the previous. Decomposes the plan into sub-tasks, wires base_branch + depends_on, embeds the closing protocol in every sub-task prompt, and polls until the stack lands.

Open Plannotator's annotation UI for a markdown file, converted HTML file, URL, or folder and then respond to the returned annotations.

Open Plannotator on the latest rendered assistant message and use the returned annotations to revise that message or continue.

Open Plannotator's browser-based code review UI for the current worktree or a pull request URL, then act on the feedback that comes back.

Generate self-contained HTML visualizations with Plannotator theming. Use for implementation plans, PR explainers, architecture diagrams, data tables, slide decks, and any visual explanation of technical concepts. Plans and PR explainers follow Plannotator's prescriptive approach; all other visual content delegates to nicobailon/visual-explainer.

Iteratively run /rereview, fix the findings, and loop until reviewers approve clean. Use for iterative automated review, when you want /rereview to loop until clean, or for a paranoid pre-merge review that auto-addresses every blocker.

Improve skills, capture context & knowledge. Use for skill iteration, capturing learnings, or upgrading agent context.

View recent screenshots from ~/Downloads. Use when the user mentions "last screenshot", "see screenshot", "recent screenshot", "show screenshot", "last N screenshots", or references viewing screenshots from Downloads. Automatically finds and displays the most recent screenshot images sorted by creation time.

Set up cross-agent skill infrastructure so skills work across Claude Code, OpenAI Codex, and GitHub Copilot. Use for multi-agent compatibility, skill migration, cross-agent sync.

Archive the current Argus task so it moves to the Archive section of the task list. Use at the end of a session when the work is done.

End-of-session checklist that detects loose ends — uncommitted changes, unmerged branches, learnings to capture, handoffs needed — and routes to the right skills. Use for session closeout, wrapping up, end of day, or "anything else to capture".

Squash all branch commits into one and update open PRs. Use when squashing commits, cleaning up history, or condensing branch commits before merge.

Show skill usage statistics, charts, and suggestions for pruning unused skills. Use when the user asks "skill usage", "which skills do I use", "unused skills", "skill stats", or "skill suggestions".

Multi-agent iterative development with parallel testing and code review. Use for building features, implementing changes, or coding tasks that need testing and review.

Generate an implementation plan from a PRD, tech spike, or feature spec and save it to context/plans/. Use for planning work, breaking down a PRD, or creating an implementation plan from a spec.

Intelligent test runner that targets changed code and identifies coverage gaps. Use for running tests, finding coverage gaps, or testing changed code.

Explain any topic in the simplest possible terms using analogies and everyday examples. Use when the user says "explain like I'm 5", "eli5", "explain simply", "dumb it down", or "explain in simple terms".

Use when the user wants to export conversation content to a professionally styled PDF for sharing

Amend the last git commit with a useful, descriptive message. Use when you want to rewrite a commit message, amend commit description, or improve the last commit message.

Compare two competing PRs implementing the same feature, identify strengths of each, and combine the best parts into a single branch. Use when comparing PRs, combining implementations, cherry-picking between PRs, or resolving competing approaches.

Analyze codebase for code smells and refactor to drastically improve code quality. Expert in clean code, SOLID principles, Ruby patterns, service objects, and refactoring. Use for code quality audits, refactoring sessions, and cleaning up technical debt.

Read Notion pages and databases using MCP tools. Use when looking up Notion content, reading pages, or querying databases.

Search and read Gmail messages. Use when looking up emails, reading email threads, or checking inbox labels.