React Hook Form Audit

Audit evidence, not syntax in isolation. A pattern becomes a finding only when its consequence is visible from the code, installed version, or verified runtime behavior.

Process

1. Establish scope and versions

Choose scope from the request before inventorying files. For a targeted bug or change review, include the requested or changed forms and follow their components, schemas, defaults, serializers, mutations, and tests. Inventory every RHF form only for an explicit repository-wide audit. Read project guidance and detect the installed RHF, React, resolver, schema, UI-library, data-fetching, and framework versions.

Completion: the scope is explicit, and every included form has an entry point and its supporting files accounted for.

2. Reconstruct each form contract