Francesco Di Lorenzo frankdilo

Review React code for unnecessary useEffect usage based on react.dev guidelines.

Arguments:

$ARGUMENTS: Optional scope to analyze (default: current git changes). Examples: "diff to main", "src/components/", "whole codebase"

Guidelines from react.dev

Before reviewing, internalize these principles:

You DON'T need useEffect for:

Accountability repo development style (detailed) — how to implement it in your repos

Purpose

This report distills the development style used in https://github.com/mikearnaldi/accountability into a reproducible playbook you can apply in your own repositories. It focuses on the workflow, artifacts, automation, and guardrails that make the "Ralph" agent loop practical and consistent.

High-level operating model (what the repo actually does)

Spec-first execution. Work is defined in specs/ documents, each with tasks/phases and status. The agent is expected to read specs, pick a task, implement, and update the spec.
Agent loop orchestration. A root script (ralph-auto.sh) runs the agent, feeds it a focused prompt, runs CI checks, and commits. The agent does not commit; the script does.
Strict CI gating. The loop requires green typecheck, lint, build, test (and optionally E2E) before commit. CI mirrors this with separate build and E2E jobs.
Full-stack alignment. `CLAUD

description
Validate implementation against plan, verify success criteria, identify issues

Validate Plan

You are tasked with validating that an implementation plan was correctly executed, verifying all success criteria and identifying any deviations or issues.

Initial Setup

description	model
Research codebase comprehensively using parallel sub-agents	opus

Research Codebase

You are tasked with conducting comprehensive research across the codebase to answer user questions by spawning parallel sub-agents and synthesizing their findings.

Initial Setup:

description
Implement technical plans from thoughts/shared/plans with verification

Implement Plan

You are tasked with implementing an approved technical plan from thoughts/shared/plans/. These plans contain phases with specific changes and success criteria.

Getting Started

description	model
Create detailed implementation plans with thorough research and iteration	opus

Implementation Plan

You are tasked with creating detailed implementation plans through an interactive, iterative process. You should be skeptical, thorough, and work collaboratively with the user to produce high-quality technical specifications.

Initial Response

Subscription Change Modal — Copy Review

This document shows all representative states of the subscription change modal copy for review.

	import { GetServerSideProps } from "next";
	import Head from "next/head";
	import { useEffect, useRef, useState } from "react";

	// I suggest to create a read-only Stripe key with access to invoices + customers for this)
	const stripe = require("stripe")(process.env.STRIPE_SECRET_KEY_INVOICE_GENERATOR);

	export default function InvoicePage(props) {
	const invoice = props.invoice;

Francesco Di Lorenzo frankdilo

Guidelines from react.dev

You DON'T need useEffect for:

Accountability repo development style (detailed) — how to implement it in your repos

Purpose

High-level operating model (what the repo actually does)

Validate Plan

Initial Setup

Research Codebase

Initial Setup:

Implement Plan

Getting Started

Implementation Plan

Initial Response

Keybase proof

Keybase proof

Francesco Di Lorenzo frankdilo

Guidelines from react.dev

You DON'T need useEffect for:

Accountability repo development style (detailed) — how to implement it in your repos

Purpose

High-level operating model (what the repo actually does)

Validate Plan

Initial Setup

Research Codebase

Initial Setup:

Implement Plan

Getting Started

Implementation Plan

Initial Response

Subscription Change Modal — Copy Review

Table of Contents

1. Upgrades (Non-Trial Users)

Keybase proof

Keybase proof