
Use when publishing or releasing a new version of an npm/pnpm/yarn/bun package to the registry. Covers package-manager detection, semver bump selection, tagging, pushing, scoped-package access, authentication, and one-time passwords (OTP).
Use when a finished worktree's branch has been reviewed and committed and needs to land. Rebases onto the latest default branch, then either fast-forwards it into the default branch (personal direct-to-main repos) or pushes it for a pull request (shared feature-branch repos).
Use when writing tests for TypeScript or JavaScript code in frameworks such as Jest, Vitest, Bun, etc.
Use when writing or modifying tests in a Bun project
Use when merging a stack of GitHub pull requests in order. Discovers the stack from the current branch, confirms with the user, then handles retargeting, merging, and branch syncing autonomously.
Use when asked to draft, write, or format a message for Slack. Produces raw text the user can copy into Slack, then format with Cmd+Shift+F.
Use when writing tests for Ruby code in frameworks such as RSpec or Minitest.
Use when writing tests for TypeScript or JavaScript code in frameworks such as Jest, Vitest, Bun, etc.
Use when explicitly instructed to create an plan (feature, bug fix, or refactor). Not for automatic use—only when directly requested.
Use when writing a TypeScript script with Bun. Covers the template, conventions, and required patterns.
Use when the user wants to run one or more generators from `@landonschropp/generate` (initialize, prettier, only-allow, eslint, typescript, jest, husky).
Use when creating Git commits.
Use when creating or updating a pull request.
Use when merging a single GitHub pull request. Handles pre-flight checks, waits for CI, and executes the merge with the repo's default method or merge queue.
Use when interacting with the user's local Neovim instance. Requires a running Neovim instance with a socket at `.agents/neovim.sock`.
Use when writing or editing a React component. Covers preferred patterns for functional components, prop types, and styling.
Use when asked to draft, write, or format a message for Slack. Produces raw text the user can copy and paste into Slack, then format with Cmd+Shift+F.
Use when working with a stack of GitHub pull requests — creating branches, keeping the stack in sync, or merging in order. Covers Git Town setup, PR targeting, rebasing, and landing the stack.
Use when needing to fixup, squash, drop, reword, reorder, or edit commits in a branch's history. Handles the non-interactive approach agents need since `git rebase -i` requires a TTY.
Use when working with files in ~/Notes (Landon's Obsidian vault). Covers vault structure (PARA), file naming, frontmatter, icons, templates, kanban boards, and the obsidian CLI.
Use when the user wants to run one or more generators from `@landonschropp/generate` (initialize, prettier, only-allow, eslint, typescript, vitest, bun-test, husky).
Use when creating, editing, evaluating, testing, or verifying ANY skill or skill-related file (SKILL.md, skill resources, skill scripts, or skill assets). If you're asked to evaluate or test a skill's effectiveness, use this skill.
Use when writing a Ruby script. Covers the template, conventions, and required patterns.
Use when setting up tmuxinator for a project, creating a new tmuxinator config, or when a project needs a terminal workspace layout.
Use when explicitly instructed to create an plan (feature, bug fix, or refactor). Not for automatic use—only when directly requested.
Use when asked to show fetch the context of the current branch
Use when analyzing Claude Code conversation logs to find patterns in repeated user instructions that could become skills. Ask for date range first.
Use when creating a new command-line script or standalone executable from scratch. Covers language selection and defers to a language-specific skill for conventions and templates.
Use when writing a Bash script. Covers the template, conventions, and required patterns.
Use when the user mentions a daily note, asks to add a task to today's daily todos, or reads or writes any file under ~/Notes/Daily Notes/. Covers location, section structure, and what each section is used for.
Use when building or updating the Work tasks section of today's daily note from Slack activity.
Use when setting up tmuxinator for a project, creating a new tmuxinator config, or when a project needs a terminal workspace layout.
Use when analyzing Claude Code conversation logs to find patterns in repeated user instructions that could become skills. Ask for date range first.
Use when creating, editing, evaluating, testing, or verifying ANY skill or skill-related file (SKILL.md, skill resources, skill scripts, or skill assets). If you're asked to evaluate or test a skill's effectiveness, use this skill.
Use when interacting with the user's local Neovim instance. Requires a running Neovim instance with a socket at `.agents/neovim.sock`.
Use when creating Git commits.
Use when asked to show fetch the context of the current branch
Use when creating or updating a pull request.
Use when merging a single GitHub pull request. Handles pre-flight checks, waits for CI, and executes the merge with the repo's default method or merge queue.
Use when merging a stack of GitHub pull requests in order. Discovers the stack from the current branch, confirms with the user, then handles retargeting, merging, and branch syncing autonomously.
Use when writing a Bash script. Covers the template, conventions, and required patterns.
Use when writing tests for Ruby code in frameworks such as RSpec or Minitest.
Use when writing a TypeScript script with Bun. Covers the template, conventions, and required patterns.
Use when writing a Ruby script. Covers the template, conventions, and required patterns.
Use when creating a new command-line script or standalone executable from scratch. Covers language selection and defers to a language-specific skill for conventions and templates.
Use when writing or editing a React component. Covers preferred patterns for functional components, prop types, and styling.
Use when building or updating the Work tasks section of today's daily note from Slack activity.
Use when splitting a working tree into atomic commits, or when changes need to be distributed across new commits and/or edits to prior commits on the branch. Especially relevant when changes within a single file belong in different commits.
Use when needing to fixup, squash, drop, reword, reorder, or edit commits in a branch's history. Handles the non-interactive approach agents need since `git rebase -i` requires a TTY.
Use when the user says "plan my morning" or wants to fill out morning journaling (Gratitude, Better Day) and personal/work tasks for today's daily note.