tidy

Tidy OCaml Code

This command analyzes and refactors OCaml code to make it more idiomatic, maintainable, and concise.

Arguments

Optional file or directory path: $ARGUMENTS (defaults to current directory)

Before You Start

Invoke the doc-style skill. Comments and documentation are part of tidying, and that skill is the standard for both.

Analysis Categories

1. Option and Result Patterns

Look for:

• Verbose match expressions that could use combinators
• Nested Option/Result handling without let*/let+
• Direct pattern matching where Option.map, Option.bind, etc. would be clearer

Transform:

(* Before *)
match get_value () with
| Some x -> Some (x + 1)
| None -> None

(* After *)
Option.map (fun x -> x + 1) (get_value ())

2. Monadic Syntax

Look for:

• Deeply nested match expressions on Result/Option
• Manual error propagation chains

Transform:

(* Before *)
match fetch_user id with
| Ok user ->
    (match fetch_perms user with
     | Ok perms -> Ok (user, perms)
     | Error e -> Error e)
| Error e -> Error e

(* After *)
let open Result.Syntax in
let* user = fetch_user id in
let+ perms = fetch_perms user in
(user, perms)

3. Pattern Matching vs Conditionals

Look for:

• Nested if/then/else chains
• Boolean condition checking that could be pattern matching

Transform:

(* Before *)
if x > 0 then
  if x < 10 then "small"
  else "large"
else "negative"

(* After *)
match x with
| x when x < 0 -> "negative"
| x when x < 10 -> "small"
| _ -> "large"

4. Code Duplication

Look for:

• Repeated error message patterns
• Similar function implementations
• Copy-pasted code blocks

Suggest:

• Helper functions
• Parameterized abstractions
• Shared error constructors

5. Module Hygiene

Look for:

• Generic module names (Util, Helpers, Common)
• Exposed record types without abstract type t
• Missing pretty-printers for main types
• Unlabeled boolean parameters

6. Comments and Documentation