fsharp-test-review

Analyze F# test code for coverage gaps and quality issues.

Updated Oct 11, 2025
One-click install
npx skills add https://github.com/bromanko/llm-agents --skill fsharp-test-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fsharp-test-review
Source: https://github.com/bromanko/llm-agents/tree/main/skills/fsharp-test-review
Command: npx skills add https://github.com/bromanko/llm-agents --skill fsharp-test-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the challenge of ensuring comprehensive and high-quality test suites for F# code, identifying gaps in coverage, and improving testing best practices.

Core Features & Use Cases

  • Coverage Analysis: Identifies missing tests for public functions, error paths, and edge cases.
  • Quality Assessment: Evaluates tests against best practices for focus, naming, assertions, and determinism.
  • Edge Case Identification: Pinpoints scenarios like empty collections, boundary conditions, and discriminated union cases that need testing.
  • Use Case: A developer can use this skill to audit an existing F# test suite, receiving actionable feedback on areas needing improvement to ensure robustness and reliability.

Quick Start

Run /review fsharp test to start an interactive test review.

Frequently Asked Questions about fsharp-test-review

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

FAQPage Schema
How do I review F# test code for missing edge cases and coverage gaps?

F# test code is reviewed by analyzing source-to-test mappings to identify coverage gaps, evaluate edge case handling, and assess adherence to testing best practices. The review scopes based on user-specified files or working changes.

What is the best way to check F# test quality and adherence to best practices?

F# test quality is checked by evaluating tests against best practices for focus, naming, assertions, and determinism. The analysis identifies skipped or disabled tests and provides findings in a structured Markdown format with severity levels.

Can I analyze a specific subset of my F# test suite instead of the whole project?

You can scope the F# test analysis to specific user-specified files or working changes. This allows the review to focus only on the relevant source code and map it directly to its corresponding tests.

How do I identify missing tests for discriminated union cases in F#?

Missing tests for discriminated union cases are identified through edge case analysis. The review pinpoints scenarios like empty collections, boundary conditions, and specific union cases that require testing.

Does the F# test review report skipped or disabled tests?

Skipped or disabled tests are explicitly identified during the F# test review. The findings are compiled into a structured Markdown format complete with severity levels for actionable feedback.

What are common edge cases to test in F# code?

Common F# edge cases to test include empty collections, boundary conditions, and discriminated union cases. The review process pinpoints these specific scenarios along with missing tests for public functions and error paths.