setup
Use when setting up a project, adding linting, formatting, git hooks, or TypeScript. Installs Biome, Husky, commitlint, lint-staged, and GitLeaks for JS/TS.
What this skill does
You are a tooling setup assistant for JS/TS projects. Auto-detect what's missing and install everything that's not already configured. ## 1. Detect Package Manager Check for lockfiles in this order: 1. `pnpm-lock.yaml` → **pnpm** 2. `bun.lock` / `bun.lockb` → **bun** 3. `yarn.lock` → **yarn** 4. `package-lock.json` → **npm** 5. No lockfile → ask the user Use the detected package manager for all install commands. Replace `<pm>` in rule files with the detected manager. ## 2. Detect Existing Tooling Before installing anything, scan for existing configurations: - `biome.json` / `biome.jsonc` → Biome already configured - `.husky/` directory → Husky already configured - commitlint config listed in `rules/commitlint.md` → commitlint already configured - `.lintstagedrc*` / `lint-staged` key in `package.json` → lint-staged already configured - `gitleaks` in `.husky/pre-commit` → GitLeaks already configured - `tsconfig.json` → TypeScript already configured - `.eslintrc*` / `eslint.config.*` → ESLint present (suggest migration to Biome) - `.prettierrc*` / `prettier.config.*` → Prettier present (suggest migration to Biome) **Skip tools that are already configured.** Report what was skipped at the end. ## 3. Install Tools Read each rule file for detailed setup instructions and config files. ### Auto-install (always set up when missing) | Tool | Purpose | Rule | |------|---------|------| | Biome | Linting + formatting | `rules/biome.md` | | Husky | Git hooks | `rules/husky.md` | | commitlint | Conventional commits | `rules/commitlint.md` | | lint-staged | Pre-commit linting | `rules/lint-staged.md` | | GitLeaks | Secrets detection | `rules/gitleaks.md` | | TypeScript | Type checking | `rules/typescript.md` | ### Opt-in (only when explicitly requested) | Tool | Purpose | Rule | |------|---------|------| | semantic-release | Automated versioning | `rules/semantic-release.md` | ## 4. Output Summary After all tools are installed, display a summary: ``` ## Setup Complete ### Installed - [list of tools installed] ### Skipped (already configured) - [list of tools skipped with reason] ### Next Steps - Run `<pm> run check` to verify Biome is working - Make a test commit to verify git hooks ``` ## 5. Supply Chain Hardening After tooling setup is complete, check if the `deps` skill is available by looking for `skills/deps/SKILL.md` relative to this skill's directory. If it exists, run `/deps` to harden the npm supply chain. If it does not exist, skip this step silently. ## Assumptions - Project has a `package.json` (JS/TS project) - GitLeaks is installed on the system (`brew install gitleaks` or equivalent) - Git is initialised in the project
Related in Code Review
gstack
IncludedFast 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)
startup-due-diligence
IncludedLegal 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.
interview-master
IncludedThis 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.
fix-issue
IncludedFixes 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.
sf-apex
IncludedGenerates 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.
swift-development
IncludedComprehensive 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.