scaffold-integration-projectlisted

Use this skill when the user wants to create a new .NET integration test project from scratch. Trigger on: "create integration test project", "scaffold integration tests", "set up integration test project", "add integration tests to my solution", "create a test project for integration tests", "I don't have an integration test project yet", "bootstrap integration test infrastructure".
jzills/Claude-Marketplace · ★ 0 · DevOps & Infrastructure · score 65

Install: claude install-skill jzills/Claude-Marketplace

# Scaffold Integration Project ## Overview Creates a complete .NET integration test project from scratch — the `.csproj`, base classes, and container configuration. Orchestrates the `setup-test-infrastructure` skill to detect and wire up service dependencies. ## Step 1 — Discover the source project Look for `.csproj` files in the repository that are NOT test projects (i.e., do not contain `<IsTestProject>true</IsTestProject>` or have names ending in `.Tests`, `.UnitTests`, or `.IntegrationTests`). If exactly one candidate is found, confirm it with the user: > "Found source project at `{path}`. Is this the project you want to test?" If multiple candidates are found, list them and ask the user to select one. If no candidates are found, ask the user to provide the path to their source `.csproj` directly. Once the source `.csproj` is identified, read it and extract: - `<TargetFramework>` — used to pin the test project's framework - `<RootNamespace>` or `<AssemblyName>` (fall back to the filename without extension) — used to derive the test namespace - All `<PackageReference>` entries — passed as context to `setup-test-infrastructure` ## Step 2 — Determine the test project location Apply the default naming convention: | Source path | Test project path | |---|---| | `src/MyApi/MyApi.csproj` | `tests/MyApi.IntegrationTests/MyApi.IntegrationTests.csproj` | | `MyApi/MyApi.csproj` | `tests/MyApi.IntegrationTests/MyApi.IntegrationTests.csproj` | Present the derived path to