Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

codemod/zod-to-valibot/src/transform/schemas-and-links/validators/brand/brand.ts (1)

3-11: ⚡ Quick win

Add required JSDoc and pure-factory annotation.

transformBrand is exported in codemod/** and appears pure, so it should include both the required JSDoc and // @NO_SIDE_EFFECTS`` marker.

Suggested patch

 import j from 'jscodeshift';
 
+/**
+ * Transforms Zod `.brand(...)` to a Valibot `v.brand(...)` action call.
+ */
+// `@__NO_SIDE_EFFECTS__`
 export function transformBrand(
   valibotIdentifier: string,
   args: j.CallExpression['arguments']
 ) {

As per coding guidelines, {library,packages,codemod}/**/*.{ts,tsx,js,jsx}: JSDoc required on exported functions (first overload only for overload sets) and Add // @NO_SIDE_EFFECTS comment before pure factory functions for tree-shaking optimization.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In
`@codemod/zod-to-valibot/src/transform/schemas-and-links/validators/brand/brand.ts`
around lines 3 - 11, The exported function transformBrand is missing required
documentation and tree-shaking optimization markers. Add a JSDoc comment block
above the transformBrand function that describes what it does, and add a //
`@__NO_SIDE_EFFECTS__` comment immediately before the function declaration to mark
it as a pure factory function for tree-shaking optimization, as required by the
coding guidelines for exported functions in the codemod directory.

Source: Coding guidelines

codemod/zod-to-valibot/src/transform/schemas-and-links/validators/brand/index.ts (1)

1-1: ⚡ Quick win

Use .ts extension in the local re-export path.

Update the re-export path to satisfy the ESM import rule enforced by ESLint.

Suggested patch

-export * from './brand';
+export * from './brand.ts';

As per coding guidelines, **/*.{ts,tsx,js,jsx}: Use ESM with .ts extensions in imports (enforced by ESLint).

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In
`@codemod/zod-to-valibot/src/transform/schemas-and-links/validators/brand/index.ts`
at line 1, In the export statement, update the re-export path from './brand' to
'./brand.ts' to include the .ts extension. This satisfies the ESM import rule
enforced by ESLint which requires explicit file extensions in import paths for
better compatibility with ES modules.

Source: Coding guidelines

codemod/zod-to-valibot/src/transform/schemas-and-links/validators/index.ts (1)

2-2: ⚡ Quick win

Align the new validator re-export with .ts extension imports.

This new local re-export should use a .ts extension to comply with the project’s ESM import rule.

Suggested patch

-export * from './brand';
+export * from './brand.ts';

As per coding guidelines, **/*.{ts,tsx,js,jsx}: Use ESM with .ts extensions in imports (enforced by ESLint).

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@codemod/zod-to-valibot/src/transform/schemas-and-links/validators/index.ts`
at line 2, The re-export statement for the brand validator is missing the `.ts`
file extension, which violates the project's ESM import rule that requires
explicit `.ts` extensions. Update the export statement to include the `.ts`
extension when re-exporting from the './brand' module to comply with the ESLint
coding guidelines.

Source: Coding guidelines