fsharp-code-review

Review F# code for idiomatic patterns and Result/Option handling.

Updated Oct 11, 2025

Search Tags:#code review #error handling #maintainability #idiomatic code #functional programming #f#

Ready to run

npx skills add https://github.com/bromanko/llm-agents --skill fsharp-code-review

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: fsharp-code-review
Source: https://github.com/bromanko/llm-agents/tree/main/skills/fsharp-code-review
Command: npx skills add https://github.com/bromanko/llm-agents --skill fsharp-code-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the need for consistent, high-quality F# code by providing automated checks for idiomatic patterns, robust error handling, and clean architectural practices.

Core Features & Use Cases

Idiomatic F# Analysis: Ensures code adheres to common F# patterns like pipeline usage, pattern matching, and computation expressions.
Error Handling Review: Checks for proper use of Result and Option types, preventing silent failures.
Architectural Guidance: Assesses module organization, type design, and naming conventions for better maintainability.
Use Case: A team lead can use this skill to quickly assess the quality of new F# contributions, ensuring they meet project standards before merging.

Quick Start

Use the fsharp-code-review skill to analyze the F# code in the 'src/MyProject' directory.

Frequently Asked Questions about fsharp-code-review

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

FAQPage Schema

How do I check if my F# code follows idiomatic functional programming patterns?▼

To check if your F# code follows idiomatic functional programming patterns, you can run an automated review that analyzes pipeline usage, pattern matching, and computation expressions against established best practices.

What is the best way to review F# error handling for Result and Option types?▼

The best way to review F# error handling is to perform an automated analysis that checks your code for proper usage of Result and Option types, ensuring there are no silent failures.

How do I assess F# module organization and type design for maintainability?▼

You can assess F# module organization and type design for maintainability by executing a code review command that evaluates your architectural practices and naming conventions.

Can I use an automated review to enforce F# coding standards before merging code?▼

Yes, you can use an automated F# code review to enforce coding standards by analyzing new contributions against a detailed checklist of functional programming best practices before merging.

Does F# code review require any specific dependencies or environment setup?▼

F# code review requires no external dependencies or complex environment setup; you simply need your F# source code directory ready to initiate the analysis process.