generate-tests

Generate green-compiling test stubs for untested public APIs.

Updated Mar 13, 2026
One-click install
npx skills add https://github.com/darylmcd/Roslyn-Backed-MCP --skill generate-tests-darylmcd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: generate-tests
Source: https://github.com/darylmcd/Roslyn-Backed-MCP/tree/main/skills/generate-tests
Command: npx skills add https://github.com/darylmcd/Roslyn-Backed-MCP --skill generate-tests-darylmcd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Batch-scaffold test stubs for untested public APIs. Use when you want to bootstrap a test project with green-compiling stubs, focused on scaffolding rather than deep coverage analysis.

Core Features & Use Cases

  • Ranks untested public APIs and selects targets based on zero-test coverage.
  • Generates lightweight, compiling test stubs to bootstrap tests for projects using Roslyn MCP.
  • Drives the Roslyn preview/apply workflow to bootstrap test projects and scaffolding while leaving actual assertions to the user.

Quick Start

Provide a top-N count, a project name, or a type name to generate green compiling test stubs.

Frequently Asked Questions about generate-tests

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate unit test stubs for untested public APIs?

Scaffolding green-compiling test stubs for untested APIs requires an active Roslyn MCP server and an accessible workspace. The Skill uses test-coverage and symbol-info data from this server to guide the generation of compiling test stubs.

Can I target specific projects or types when scaffolding tests?

Yes, you can scope target APIs for scaffolding tests by providing a top-N count, a specific project name, or a type name. This allows you to tailor the test generation workflow to focus on particular areas of your codebase.

Does the test scaffolding workflow write assertions for me?

No, the test scaffolding workflow focuses on bootstrapping test projects by generating compiling stubs rather than deep coverage analysis. It drives the Roslyn preview and apply workflow to create stubs while leaving actual assertions to the user.

What's the best way to bootstrap a test project with green-compiling stubs?

The best way to bootstrap a test project with green-compiling stubs is to use this Skill with your Roslyn workspace. It ranks untested public APIs, selects targets based on zero-test coverage, and generates lightweight stubs that compile successfully.

Why do I need a Roslyn MCP server to generate test stubs?

A Roslyn MCP server is required to generate test stubs because the Skill relies on it to access the loaded workspace and retrieve test-coverage and symbol-info data. This data guides the identification and scaffolding of untested public APIs.