Test Scaffolding Skill

Generate test file scaffolds for source files, enabling TDD workflows. Scaffolds contain TODO stubs that the test-engineer agent fills during lane execution.

Variables

Workflow (Mandatory)

1. Detect stack: Read package manifest (pyproject.toml, package.json, go.mod, Cargo.toml)
2. Identify framework: Match test dependencies (pytest, vitest, jest, testing, cargo test)
3. Analyze sources: Extract public functions, classes, methods from each source file
4. Map to tests: Apply naming convention to determine test file paths
5. Generate scaffolds: Use language template, insert TODO stubs for each testable unit
6. Return manifest: JSON with generated files, skipped files, and unit counts

Supported Frameworks

Naming Conventions

Source Analysis Heuristics

Python

• Detect def function_name( where name doesn't start with _
• Detect class ClassName: for public classes
• Extract method signatures within classes
• Skip __init__, __str__, etc. (dunder methods)

TypeScript/JavaScript

• Detect export function, export const, export class
• Detect export default function/class
• Parse JSDoc/TSDoc for parameter types

Go

• Detect exported functions (capitalized names)
• Detect exported methods on structs
• Detect exported types

Rust

• Detect pub fn, pub struct, pub enum
• Detect impl blocks with public methods

Output Schema

{
  "format": "scaffold-manifest/v1",
  "generated_at": "<ISO-8601 UTC>",
  "framework": "pytest",
  "generated": [
    {
      "source": "src/auth/login.py",
      "test": "tests/auth/test_login.py",
      "units": ["login", "logout", "refresh_token"],
      "unit_count": 3
    }
  ],
  "skipped": [
    {
      "source": "src/auth/utils.py",
      "reason": "test file exists"
    }
  ],
  "total_units": 12
}

Red Flags (Stop & Verify)

• No package manifest found → prompt user for framework
• Source file has no public functions → skip with warning
• Test file already exists → skip unless --force specified
• Unable to parse source file → log warning, continue with others

Integration Points

With /ai-dev-kit:plan-phase

• Called to auto-populate Tests Owned Files column
• Uses Owned Artifacts from impl tasks as source files

With /ai-dev-kit:execute-lane

• Called before test-engineer agent runs
• Scaffolds committed with chore(P{n}-{lane}): scaffold test files

With test-engineer agent

• Agent detects TODO markers in scaffolds
• Fills in test implementations
• Removes TODO markers when complete

Provider Notes

• Use this skill when /ai-dev-kit:scaffold-tests is invoked
• Prefer TODO-style stubs over skip markers for visibility
• Preserve source file structure in test organization
• Include proper imports based on detected framework