shorted prompt cuz otherwise it keeps on hallucinating

Author: vic-stan

workflow.yaml

@@ -13,7 +13,7 @@ nodes:
     type: automatic
     steps:
       - name: "Transform React class components to function components"
-        run: "npx -y @codemod/cli@3.3.0 --plugin ../../../react-declassify/cjs/dist/index.js src/"
+        run: "npx -y @codemod/cli@3.3.0 --plugin ../../../react-declassify/cjs/dist/index.js ${TARGET:-src/} || true"
   - id: ai-review
     name: "AI Review"
     type: automatic
@@ -26,47 +26,7 @@ nodes:
           model: "gpt-4o-mini"
           max_tokens: 8000
           prompt: |
-            IMPORTANT: A codemod (`react-declassify`) has ALREADY attempted to transform React class components to function components in this repository.
-            Most files are COMPLETE, but `react-declassify` has known limitations and leaves markers where it fails. Your job is to REVIEW, FIX, and FINISH the transformations.
+            You are reviewing React component migrations.
+            Only if you see `react-declassify-disable` or `TODO_this` in the provided files, fix the component to use Hooks.
+            If the file looks fine and does not have these markers, return immediately with no changes. Do not output any verbose explanations.
 
-            CRITICAL: You MUST provide verbose output explaining what you're doing at each step!
-            Output your progress as you work so users can see what's happening.
-
-            Step 1: Search for Hard Errors and Soft Errors
-            - Search the project for `react-declassify-disable Cannot perform transformation`. This indicates a HARD ERROR where the tool gave up. You MUST manually convert this entire class to a function component with Hooks yourself!
-            - Search the project for `TODO_this`. This indicates a SOFT ERROR where the tool didn't know how to bind or resolve `this`. Fix the scoping and state/prop references.
-
-            Step 2: Address react-declassify's Known Limitations
-            - Class Refs: If the old class was receiving refs or being instantiated via `useRef`, the new functional component will break. You MUST wrap the component in `React.forwardRef` and use `useImperativeHandle` to expose the necessary methods/properties!
-            - Stricter Render Types: If the component returns a bare string/number and TypeScript complains about `FC<Props>`, wrap the return statement in a fragment `<> ... </>`.
-
-            Step 3: Review common transformation issues
-            - Fix missing or incorrect dependency arrays in useEffect hooks
-            - Ensure all setState calls use the functional updater when depending on previous state
-            - Add missing cleanup functions in useEffect where needed
-
-            Step 4: ALWAYS output a clear summary
-            You MUST provide a detailed summary at the end including:
-            - Total files reviewed
-            - List of ACTUAL files you modified (use real file paths)
-            - Specific changes made to each file (e.g., "Resolved TODO_this", "Added forwardRef")
-
-            try `npm run build`-ing to validate.
-
-
-            Output format:
-            ```
-            📊 AI Review Summary
-            ==================
-            Files reviewed: [actual number]
-            Files modified: [actual number]
-
-            Changes made:
-            1. [ACTUAL FILE PATH]
-               - [specific change]
-            ```
-
-            **Efficient Review Strategy:**
-            - Run: grep -r "TODO_this" --include="*.js" --include="*.jsx" --include="*.tsx" --include="*.ts" .
-            - Run: grep -r "react-declassify-disable" --include="*.js" --include="*.jsx" --include="*.tsx" --include="*.ts" .
-            - Only modify files that have actual problems. If the transformation is already correct, don't modify the files.