Claude Skills by LandonSchropp

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 closing a herdr workspace or worktree. Confirms nothing in the checkout would be lost, then removes the worktree and closes the workspace.

Use when work belongs somewhere other than this session: a different repository, an asynchronous task queue, or a visual design tool, so an agent with the right environment and context does it instead.

Use at the start of any task, before taking action, to load the always-on workflow rules covering skill invocation, communication, test-driven development, reviews, and skill scripts.

Invoke after the agent has stopped, whether the user interrupted it or it paused on its own, to have it resume and stop asking for permission it doesn't need for the rest of the conversation.

Use when a task needs its own checkout of a project — delegating work to another agent, or starting a branch that should run alongside the current one — and a herdr workspace has to be opened for it.

Use when a session's job is to hand work out to other agents rather than do it — running a set of tasks across several projects or worktrees, a stage at a time.

Use when several tasks are going out to separate agents at once and the work needs splitting into what can run simultaneously and what has to wait, before any of it is kicked off.

Use when instructed to create a plan (feature, bug fix, or refactor).

Invoke when the agent's conversational replies have gotten too long or wordy and the user wants shorter answers for the rest of the conversation.

Use when a task needs a browser — reading a page, filling a form, taking a look at something, or reaching anything behind a login. Always run this skill before the `playwright-cli` skill.

Use when writing or editing a code comment or a documentation block, and when reviewing the comments and documentation in a diff before presenting it. Decides what stays in the source, what moves to reference documentation, and what gets deleted.

Use when a commit's changes are finished and about to be presented for review. Runs the checks that catch the objections the user would otherwise raise, before they spend time reviewing.

Use when setting up a new personal project, or when deciding which root file a piece of documentation, configuration, environment variable, or agent instruction belongs in. Covers the standard root files and what each one owns. Does not cover source code layout.

Use when creating or editing a macOS LaunchAgent for a recurring or scheduled script. Covers plist structure, PATH resolution, multiple trigger times, the reload workflow, and which behaviors launchd already handles so they don't need to be rebuilt.

Use when creating a note, document, script or project that shouldn't outlive a known date — interview prep, a migration, a course, a time-boxed experiment — so it gets deleted on time instead of rotting in the repository.

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 creating Git 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 a finished, reviewed branch is committed and needs to be merged into the default branch in a repo that integrates directly to `main` (not via pull request).

Use when opening a GitHub issue, bug report, feature request, or discussion in any repository, including one the user has no local checkout of.

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

Temporarily turn off the requirement that pending changes be reviewed before committing in the current herdr workspace.

Turn interactive commit reviews back on for the current herdr workspace.

Runs an interactive command in a separate window and waits for it to close, and covers closing a herdr tab safely. Invoked only when another skill explicitly calls for it, never on its own.

Use when a skill needs the user to interactively edit a file in Neovim mid-workflow, then read their changes back. Takes a window name and the file to edit.

Use when a skill needs the user to interactively review code changes in revdiff mid-workflow — working changes, staged changes, or a specific commit — then read their annotations back. Takes a review mode.

Contains interactive interaction scripts. Use when another skill explicitly instructs invoking this one. Do not invoke on your own initiative.

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 the user wants flash cards, a spaced-repetition deck, or a Mochi deck built from a note, a course, a book or any other source material.

Use when working with files in ~/Notes (the user's Obsidian vault). Covers vault structure (PARA), file naming, frontmatter, icons, templates, kanban boards, and the obsidian CLI.

Use when the user says "plan my morning" or wants to fill out morning journaling (Gratitude, Better Day, Daily Affirmation) and personal/work tasks for today's daily note.

Use when reading or writing files under ~/Notes/Projects/, starting a new project, or archiving a finished one. Covers folder layout, the board file, supporting notes, and the project lifecycle across Future/, Projects/, and Archive/.

Use when writing tests for Ruby code in frameworks such as RSpec or Minitest.

Use when writing a Bash script. Covers the template, conventions, and required patterns.

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 the user wants to run one or more generators from `@landonschropp/generate` (initialize, prettier, only-allow, eslint, typescript, vitest, bun-test, husky).

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 writing or editing a React component. Covers preferred patterns for functional components, prop types, and styling.

Use when writing or modifying tests in a Bun project

Use when writing or modifying tests for Ink (terminal UI) components.

Use when writing or modifying tests for React hooks.

Use when writing tests for TypeScript or JavaScript code in frameworks such as Jest, Vitest, Bun, etc.

Use when a writer wants to improve a draft through guided questioning and revision rather than a direct rewrite

Use when an outline or bullet points need expanding into a fully developed document with complete paragraphs

Use when a document needs the writer's structural and formatting conventions applied