react-hook-form-audit
/react-hook-form-audit
Audit existing React Hook Form code for correctness, accessibility, validation, data ownership, submission, dirty-state, field-array, wizard, controlled-widget, and performance problems. Use when reviewing RHF forms, investigating form bugs or rerenders, or checking an RHF-heavy change. Read-only; use react-hook-form for implementation.
- Author
- kriscard ↗
- Repository
- Skills ↗
- Licence
- MIT
- Last repository change
- 25.10.2026
Assessment and security
- Files in this package
- 8
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 25.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Audit existing React Hook Form code for correctness, accessibility, validation, data ownership, submission, dirty-state, field-array, wizard, controlled-widget, and performance problems. Use when reviewing RHF forms, investigating form bugs or rerenders, or checking an RHF-heavy change. Read-only; use react-hook-form for implementation.
Original author description
Audit existing React Hook Form code for correctness, accessibility, validation, data ownership, submission, dirty-state, field-array, wizard, controlled-widget, and performance problems. Use when reviewing RHF forms, investigating form bugs or rerenders, or checking an RHF-heavy change. Read-only; use react-hook-form for implementation.
How it works
- Process
- Hard boundaries
SKILL.md preview
--- name: react-hook-form-audit description: >- Audit existing React Hook Form code for correctness, accessibility, validation, data ownership, submission, dirty-state, field-array, wizard, controlled-widget, and performance problems. Use when reviewing RHF forms, investigating form bugs or rerenders, or checking an RHF-heavy change. Read-only; use react-hook-form for implementation. --- # 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 For each form, identify: - form and payload types; - create/edit and server-data ownership model; - default-values and dirty baseline; - native versus controlled adapters; - validation and error paths; - conditional, wizard, and field-array behavior; - submission, success, failure, and reset lifecycle. Completion: each submitted value can be traced from initialization through serialization. ### 3. Run the checks Read `references/checks.md` completely. Load the bundled mirror of the build skill's canonical branch reference when the audited form uses that branch: - `references/server-data-and-lifecycle.md` - `references/adapters-and-accessibility.md` - `references/wizards-and-conditionals.md` - `references/field-arrays.md` - `references/version-8.md` - `references/actions-boundary.md` Completion: every applicable check and branch rule was evaluated against every in-scope form. ### 4. Validate findings Use source and types to distinguish a defect from a heuristic smell. Run the project's TypeScript typecheck; do not modify source to make it pass. Tests are optional—run focused existing tests when they can prove or disprove a suspected behavior. Prefer silence over speculative findings. Completion: each reported finding has a concrete consequence, file and line, smallest safe direction, and confidence; unrelated typecheck failures are separated. ### 5. Report Order findings by user impact: - **Critical:** data loss, invalid submission, inaccessible completion, or broken production flow. - **High:** likely correctness/reliability failure in a common path. - **Medium:** demonstrated performance, maintainability, or UX cost. - **Low:** verified local issue with limited impact. Use: ```text [Severity] Short title File: path:line Evidence: what the code does and the scenario that exposes it Impact: concrete user or engineering consequence Direction: smallest safe correction Confidence: high | medium ``` Then list forms reviewed, typecheck command/result, tests run or skipped, and residual risks. If no findings survive validation, say so directly. ## Hard boundaries - Remain read-only; report files are allowed only when the user requests one. - Do not label `watch`, `Controller`, `useFormContext`, missing defaults, `onChange`, or `useActionState` as defects without contextual evidence. - Do not claim performance impact without identifying the subscription and rerender boundary or measuring it when measurement is feasible. - Do not infer App Router client-boundary requirements in Pages Router or non-Next projects.
Files in this package (8)
- SKILL.md 4 KB
- references/actions-boundary.md 1 KB
- references/adapters-and-accessibility.md 3 KB
- references/checks.md 5 KB
- references/field-arrays.md 1 KB
- references/server-data-and-lifecycle.md 3 KB
- references/version-8.md 1 KB
- references/wizards-and-conditionals.md 2 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · kriscard/Skills | 100 | MIT |
| pproenca/dot-skills | 100 | MIT |
Database snapshot: 13.11.2026 · package version afc6991f2400 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100react-hook-form
React Hook Form with Zod validation. Covers form setup, validation schemas, field components, error handling, and submission with shadcn/ui integration. USE WHEN: user mentions "React Hook Form", "RHF", "Zod validation", "shadcn/ui forms", "zodResolver", "FormField", asks about… - 100react-hook-form
Build and modify forms that use React Hook Form or whose project conventions require it. Use when implementing controlled widgets, schema validation, fetched edit forms, conditional fields, multi-step wizards, field arrays, submission errors, or dirty-state handling. For review… - 95react-form-validator
This skill should be used when the user asks to "create a form", "add validation", "handle form submission", "use React Hook Form", or when creating login, signup, or data entry forms. Enforces React Hook Form + Zod pattern. - 95react-hook-form-zod
Type-safe React forms with React Hook Form and Zod validation. Use for form schemas, field arrays, multi-step forms, or encountering validation errors, resolver issues, nested field problems. - 100react-hook-form
React Hook Form performance optimization for client-side form validation using useForm, useWatch, useController, useFieldArray, the subscribe() API, and the Watch / FormStateSubscribe / FieldArray render-prop components. Covers RHF 7.82 additions including resetDefaultValues()… - 90frontend-form-handling
Use this skill when the user says 'form handling', 'form validation', 'React Hook Form', 'Formik', 'form state', 'form submission', 'field validation', 'form error', 'controlled input', 'uncontrolled input', 'form schema', 'Zod validation', 'form dirty', 'field array'. Implement…