dotfiles

Use when the user says "capture", or wants to remember, save, or note something for later.

Use when the user says "closeday", "close my day", or "end of day". End-of-day consolidation appended to today's Inbox note.

Use when the user says "today", "morning plan", "plan my day", "what should I work on", or asks about their priorities for the day.

Use whenever `jj root` succeeds. Use `jj` for all version-control operations; do not use `git`.

Use when the user asks to create a GitHub issue, file a bug, or track a task. Also use when the user describes a problem they found and wants to capture it.

Use when the user asks to open a PR, create a PR, or push and create a pull request.

Use when parallel isolation is needed — multiple agents/sessions working on the same jj repo, or when the user asks to work in a separate workspace without disturbing their current @.

Use when the user needs to investigate a topic before designing — library landscape, prior art, codebase patterns, best practices. Produces a research brief in docs/refs/.

Use when a plan exists (in `.opencode/plans/` or approved in the current conversation) and is ready to execute. Dispatches subagents per task with review gates.

Use when the user wants to design, plan, or scope a feature, fix, or change before implementing it. Produces specs and implementation plans.

Use when the project uses jj (Jujutsu) for version control instead of git. Load this after `jj root` succeeds.

Use when the user asks to open a PR, create a PR, or push and create a pull request.

Use when working on dotfiles or configuration files in ~/.config. Load this skill when editing, adding, or managing files tracked by the dotfiles repository.

Use when the user wants to make a cross-cutting architectural decision. Guides exploration of the decision space and produces an ADR (Architecture Decision Record) in docs/adrs/.

Use when the user asks to create a GitHub issue, file a bug, or track a task. Also use when the user describes a problem they found and wants to capture it.

Use when encountering any bug, test failure, or unexpected behavior. Enforces root cause investigation before proposing fixes.