dotfiles

Analyze the changes in the current Jujutsu (jj) changeset and give it a clear, concise description with type and scope trailers. Use when the user asks to describe a change or commit.

Read and parse jj logs, commit messages, and descriptions. Use when the agent needs to inspect commit history, search for commits by message content or trailers, filter by author/date/branch, parse jj log output into structured data (subject, body, type/scope trailers), or navigate jj revision ranges. Triggered by requests to "show git log", "find commits with fix", "what changed in this branch", "list recent jj commits", or any history browsing task.

Read ShopifySharp source code and map GraphQL response types to application models. Use when working with ShopifySharp library, converting GraphQL API responses to C# or F# types, or understanding Shopify's generated types.

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends the agent's capabilities with specialized knowledge, workflows, or tool integrations.

Split the current Jujutsu (jj) changeset into smaller, logically separate commits using non-interactive `jj split` with filesets. Use when the user asks to break up a change, split the working copy, separate unrelated edits into their own commits, stack a messy change into clean commits, or otherwise reshape one jj revision into several. Covers jj >= 0.42 topology, working-copy placement, and verification.

Break up the pending git changes into small, logical commits and commit them using well-structured commit messages.

Generate a well-structured git commit message based on staged changes.

Generate a well-structured jj describe message based on staged changes.

Open or jump to a file location in an existing Neovim instance via nvr (neovim-remote).

Create a GitHub pull request for the current branch with minimal description and appropriate labels.