skills/generate/SKILL.md
Use when the user wants to run one or more generators from `@landonschropp/generate` (initialize, prettier, only-allow, eslint, typescript, jest, husky).
npx skillsauth add LandonSchropp/agent-toolkit generateInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Fetch the readme from https://github.com/LandonSchropp/generate to confirm the current generator list and canonical order. Do NOT rely on memory — the list changes.
Present the generators to the user and ask which ones to run. Preserve the readme's documented order.
Run --help on every selected generator BEFORE asking the user anything:
pnpx @landonschropp/generate <generator> --help
Collect every flag across every selected generator. Identify conceptual overlaps — the same question may appear under different flag names (e.g. jest's --react, husky's --react, and eslint's --plugins checkbox all ask about React). Ask the user ONCE for each conceptual question.
--help lists flag names and messages but not enumerated choices for list or checkbox prompts. When the allowed values for a flag are unclear, read the generator's source on GitHub (e.g. https://raw.githubusercontent.com/LandonSchropp/generate/main/src/<generator>/index.js) — the choices array lists every valid value.
Ask the user for the consolidated inputs. Do not start running generators until you have answers for every required flag across every selected generator.
Invoke each selected generator in the readme's canonical order, passing every answer as --flag=value. Example:
pnpx @landonschropp/generate typescript --type=node --outDir=
pnpx @landonschropp/generate jest --typescript=true --react=false
| Thought | Reality |
| ----------------------------------------------- | ---------------------------------------------------------------------------------------- |
| "Positional args are shorter" | Positional order is undocumented and fragile. Always use --flag=value. |
| "I'll ask as I go, one generator at a time" | That defeats dedup. Gather flags from ALL selected generators' --help first, then ask. |
| "The CLI will prompt for anything I miss" | No. Run non-interactively. If a flag is missing, ask the user first, then invoke. |
| "I already know the generator list from memory" | Fetch the readme. Generators and their flags change — the readme is the source of truth. |
| "Running --help on 5 generators is wasteful" | It takes seconds and prevents repeated questions. Always do it up front. |
tools
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).
tools
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.
tools
Use when writing or modifying tests in a Bun project
tools
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).