- Home
- Skills
- Frontend & Web Apps
- Catch list-page bugs before bulk actions hit wrong rows
Catch list-page bugs before bulk actions hit wrong rows
Does not run the app, edit code or review styling, performance or accessibility.
$6
Works with the AI Agents you already use
Catch list-page bugs before bulk actions hit wrong rows
Example session with this skill installed
Audit our Users admin page before release: UsersPage.tsx, UsersTable.tsx, BulkBar.tsx and the API handler users.handler.ts. Admins search, filter by status, sort columns and bulk-block users.
- Read your context and instructions
- Compiled the catch list-page bugs
- Generated the document
List page audit: Users (UsersPage.tsx, UsersTable.tsx, BulkBar.tsx, users.handler.ts)
Verdict: 2 Critical, 5 High, 3 Medium, 2 Low — fix B4 and B3 before anyone uses "Block".
State map
| State | Lives in | Written by | Read by | Resets when |
|---|---|---|---|---|
| page | URL ?page | goToPage | effect request, Prev button | never (not on search/status change) |
| search | component state (seeded once from URL ?q) | input onChange | effect request | never; URL not updated |
| status | component state | select onChange | effect request | never; not in URL |
| sortBy | component state | header click | client-side sorted only | never; not sent to server |
| selected | component state, row indexes | checkbox | BulkBar, blockSelected | only after a bulk action |
| rows / total | component state | effect .then | table, "N users" | overwritten in arrival order |
Findings (most severe first)
[Critical] B4 Selection is stored as row index, and the index points into the client-sorted array
Evidence: UsersTable.tsx — checked={selected.includes(i)} onChange={() => onToggle(i)}; UsersPage.tsx — const ids = selected.map((i) => sorted[i].id);
Scenario
- Tick Alice and Bob (rows 0 and 1).
- Click the "Name" header.
- The ticks stay on rows 0 and 1, now different users.
- Block → the wrong two users are blocked.
Fix: store selected ids (Set<string>), toggle withr.id, send[...selected].
Confidence: confirmed from code
[Critical] B3 Selection survives search, status and page changes
Evidence: setSelected([]) is called only inside blockSelected.
Scenario
- Tick rows 3 and 4.
- Type "smith".
- BulkBar still says "2 selected".
- Block → whichever "smith" users sit at positions 3 and 4 are blocked; on a shorter list
sorted[i].idthrows.
Fix: clear selection whenever page, search, status or sort changes.
Confidence: confirmed from code
[High] A1 Sorting by column sorts only the 25 rows of the current page
Evidence: const sorted = [...rows].sort(...); sortBy is never sent; server always sorts { createdAt: -1 }.
Fix: send sort to the server, allowlist it there, drop the client sort.
[High] C1 Older search response can overwrite a newer one
Evidence: effect .then(res => setRows(res.rows)) with no cleanup/abort; search changes per keystroke.
Scenario (slow network): type "jo" then "jon"; the "jo" response lands last → input says "jon", table shows "jo".
Fix: ignore flag in the effect cleanup, or a keyed query hook; debounce input.
[High] F2 Total count ignores the search filter
Evidence: users.handler.ts — page query uses filter, count uses { status: filter.status }.
Fix: User.countDocuments(filter).
[High] E2 After "Block", the list does not refetch
Evidence: goToPage(page) pushes the same ?page=; effect deps [page, search, status] don't change.
[High] F1 Server sort has no unique tie-breaker
Fix: .sort({ createdAt: -1, _id: -1 }). Confidence: likely, depends on how often createdAt repeats.
[Medium] B1 Search/status change keeps the page number → "No users found" on page 8 of 1
[Medium] G1 A failed request is shown as "No users found"
[Medium] F3 No upper bound on page size
[Low] D1 Search read from the URL once; status not in the URL
[Low] D2 ?page=abc gives NaN on the client
Questions
- Is the page meant to be shared by link? If yes, D1 rises to Medium.
- What does your Mongoose/driver config do with
{ status: undefined }in the count?
Not checked
- Server side of
api.blockUsers(scoping of ids).
Outside this audit
req.query.qgoes into$regexunescaped — worth a security review.
UsersPage.tsx
PDF · document
Example file from a real run - the skill writes it into your workspace.
Connects securely to your tools. The creator never sees your data.
About this skill
Why
Admin tables look fine in a demo with 12 rows. In production, a column sort only sorts the current page, a search response from two keystrokes ago overwrites the new one, and a selection kept by row index makes "Block 2 users" block the wrong two. None of this fails TypeScript or lint.
What it checks
The skill first builds a state map (where page, page size, sort, filters, search, selection and totals live, who writes them, when they reset), then runs seven groups of checks:
- Scope — client-side sort/filter/search on a server-paginated page, totals from page length, "select all" and export that don't match their labels
- Reset rules — page not reset on filter change, selection surviving filter/sort/page changes, selection keyed by index instead of id
- Request ordering — late responses overwriting newer ones, query keys missing a parameter, debounced input clobbered by URL sync, bulk actions enabled while placeholder rows are on screen
- URL state — double sources of truth, unvalidated
page/sortvalues, history spam - Bulk actions — what's sent vs what was confirmed, missing refetch/rollback, double-fire, server-side scoping of ids (if the server code is provided)
- Server pagination — sort without a unique tie-breaker, count and page queries using different filters, uncapped page size
- States — errors rendered as "No results"
What you get
A verdict line, the state map, findings ranked Critical → Low (Critical is reserved for actions on rows the user did not see or confirm), each with evidence, a reproduction a tester can follow, a minimal fix and a confidence label. Then open questions and what was not checked.
Limits
Reads files only (optionally read-only git diff/log/show). Does not run the app, edit code or review styling, performance or accessibility. Library notes (TanStack Query v5, Next.js App Router search params, MongoDB/SQL tie-breakers) were checked against official docs in November 2026.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Frontend & Web Apps.
Reviews list-state correctness only: no styling, accessibility, performance or general security review (serious unrelated issues get a one-line pointer). Does not execute code, so timing bugs are reported with the conditions needed to reproduce them, not reproduced. Server-side checks need the server handler. Not built for virtualised infinite-scroll feeds or spreadsheet-style editable grids.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 4 days ago
- Software
Git
Permissions
File Scopes
read/grep/glob: to open and search the list page, its data hook and server handler. bash is optional and limited to read-only git commands (git diff, git log, git show) to focus on changed code; the skill never writes files, installs packages, runs the app or contacts any network host.