create-tests-extract
Extract large inline test modules into adjacent test files while preserving the same effective visibility, helper access, and coverage shape. Use when the user wants implementation files slimmed down without accidentally turning private unit tests into weaker integration tests.
What this skill does
<EXTREMELY-IMPORTANT> The point is readability without semantic drift. Non-negotiable rules: 1. Read the source file and its inline tests fully before moving anything. 2. Preserve the original visibility and helper access model. 3. Prefer adjacent test modules over integration tests when private access matters. 4. Change production code only as much as module wiring requires. 5. Run the narrowest relevant tests after extraction. </EXTREMELY-IMPORTANT> # create-tests-extract ## Inputs - `$request`: Source file, module, or cleanup goal ## Goal Move bulky inline tests into adjacent files while keeping: - the same effective test coverage - the same access to private items where needed - a clearer production file ## Step 0: Read and classify the test block Inspect: - the production file - the inline test module - helper functions or fixtures used only by tests - whether the tests depend on `super::*` or private module items If the file belongs to a Rust crate, use `rust` for conventions before changing the module layout. **Success criteria**: The tests are classified as local-inline, adjacent-module, or true integration candidates. ## Step 1: Choose the smallest safe extraction boundary Prefer: - `foo.rs` + `#[cfg(test)] mod foo_tests;` + `foo_tests.rs` - or `foo/mod.rs` + `tests.rs` for directory modules Avoid pushing tests into top-level `tests/` unless they genuinely should become public-API integration tests. **Success criteria**: The new layout preserves the intended visibility model. ## Step 2: Extract without semantic drift When moving the tests: - add the minimal `#[cfg(test)] mod ...;` wiring - keep `use super::*;` or equivalent imports when needed - preserve test names and attributes - move test-only helpers with the suite that needs them Do not rename tests or restructure production modules unless the extraction requires it. **Success criteria**: The moved tests still compile in the same effective context. ## Step 3: Verify the moved suite After extraction: - run the narrowest relevant tests - check for warnings or visibility regressions - verify the production file is materially easier to scan **Success criteria**: The new layout passes and preserves behavior. ## Guardrails - Do not turn private unit tests into public-only integration tests by accident. - Do not move tiny, explanatory inline tests that still improve readability where they are. - Do not broaden the refactor beyond the requested extraction. - Do not drop fixtures or helper coverage just to shorten the production file. ## Output Contract Report: 1. files created or modified 2. extraction layout chosen 3. any tests intentionally left inline 4. validation run after the move
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.