dotfiles

Use when operating on the Linear issue tracker via the `linear` CLI: creating, viewing, searching, querying, or updating issues, projects, or documents; adding or editing issue comments; managing relations, links, labels, and teams; assigning, labeling, or transitioning issues. Triggers on phrases like "create a Linear issue", "file a ticket", "update ENG-###", "move to Ready For Dev", "search for issues", "find issues about X", "add a comment to the Linear issue", "link a PR to the issue", "block ENG-42", or any task naming Linear, a Linear issue key (`ENG-`, `OPS-`, etc.), a Linear project, or a Linear document. Do NOT use for GitHub Issues, Jira, or other trackers.

Use when creating, editing, refactoring, or reviewing AGENTS.md files at any level (repo, package, or global). Triggers on phrases like "update AGENTS.md", "add a rule to AGENTS.md", "global directives", or any edit to a file named AGENTS.md (including chezmoi source forms). Do NOT use for SKILL.md, agent definitions, or slash commands.

Use when creating, editing, refactoring, or reviewing OpenCode custom slash commands; writing or revising command frontmatter, arguments, agent routing, or permissions. Triggers on phrases like "new slash command", "add a /command", "edit the command file", or any edit to files in a commands directory (including chezmoi source forms). Do NOT use for AGENTS.md, SKILL.md, or agent definitions.

Use when creating, editing, refactoring, or reviewing SKILL.md files and skill directories. Triggers on any edit to a SKILL.md file or skill directory (including chezmoi source forms). Do NOT use for AGENTS.md, agent definitions, or slash commands.

Use when creating, editing, or refactoring custom OpenCode agent definitions (`.md` or `.md.tmpl` files in an agents directory, including chezmoi source forms). Triggers on any edit to an agent definition file. Do NOT use for AGENTS.md, SKILL.md, or slash commands.

Use when reading, posting, or managing PR review comments via the `gh-review` tool: viewing PR comments with filtering, leaving inline comments on specific diff lines, starting or deleting pending reviews, replying to review threads, editing or removing individual review comments. Triggers on phrases like "review this PR", "check for comments", "leave a comment on line X", "add review feedback", "start a pending review", "reply to the comment", "edit the comment", "remove that comment", "delete that comment", "fix my comment", "move comment to line X", or any task involving PR comments and code review. Do NOT use for merging, approving via `gh pr review --approve`, or non-review PR operations.

Use when creating, editing, refactoring, or reviewing modularized Python CLI scripts managed by uv with pyproject.toml; scaffolding new script projects; adding commands or subcommands to Click-based CLIs; writing pytest tests for CLI tools; configuring hatchling builds or dependency groups; creating wrapper shell scripts for uv-managed projects. Triggers on phrases like "new python script", "add a CLI command", "scaffold a script project", "python CLI", "click command", or any work in a scripts/ directory containing pyproject.toml with hatchling. Do NOT use for single-file scripts, Jupyter notebooks, web applications, or Django/Flask projects.

Use when operating on the GitHub REST or GraphQL API via `gh api` for cases not covered by higher-level `gh` subcommands: creating or managing draft pull requests, querying or mutating GitHub Discussions, or any GitHub API call requiring raw endpoints. Do NOT use for standard `gh pr`, `gh issue`, `gh release`, or `gh repo` workflows. Do NOT use for any PR review operations (reading comments, posting replies, managing reviews); use `gh-review` instead.

Use when writing prose text to files or through tool calls: documentation, changelogs, pull request or issue descriptions and comments, email drafts, READMEs, release notes, announcements, blog posts, gist content, or any durable written artifact. Do NOT use for in-session conversational responses, code, commit messages, or structured data (JSON, YAML, tables).

Use when staging individual hunks or partial changes within a file non-interactively (scripted replacement for `git add -p`): splitting a file's changes across multiple commits, staging only selected lines or regions, or selecting hunks in automated workflows where terminal interaction is unavailable. Triggers on phrases like "stage this hunk", "split this commit", "partial add", or "commit only part of this file".