generate

Included with Lifetime

$97 forever

Use when the user wants to run one or more generators from `@landonschropp/generate` (initialize, prettier, only-allow, eslint, typescript, vitest, bun-test, husky).

Code Review

What this skill does

## Process

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

2. **Present the generators** to the user and ask which ones to run. Preserve the readme's documented order.

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

4. **Ask the user for the consolidated inputs.** Do not start running generators until you have answers for every required flag across every selected generator.

5. **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 vitest --react=false
```

## Rationalizations

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

Files: 1

Size: 2.7 KB

Complexity: 11/100

Category: Code Review

Source: https://github.com/landonschropp/agent-toolkit/tree/main/plugins/ls-typescript/skills/generate

Related in Code Review

gstack

Included

Fast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)

Code Reviewscriptsfeatured

startup-due-diligence

Included

Legal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.

Code Reviewscripts

interview-master

Included

This skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.

Code Reviewscripts

fix-issue

Included

Fixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.

Code Reviewscripts

sf-apex

Included

Generates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.

Code Reviewscripts

swift-development

Included

Comprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.

Code Reviewscripts