ls

Add specs using a structured testing approach

Add tests using a structured testing approach

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 analyzing Claude Code conversation logs to find patterns in repeated user instructions that could become skills. Ask for date range first.

Use when interacting with the user's local Neovim instance. Requires a running Neovim instance with a socket at `.agents/neovim.sock`.

Use when explicitly instructed to create an plan (feature, bug fix, or refactor). Not for automatic use—only when directly requested.

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 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.