What is architecture-review?

Ideal for Code Review Agents specializing in Next.js, Supabase, and SWR, seeking to enhance codebase health and detect issues. Scans Mesh codebase for duplicated code, bad patterns, complexity hotspots, and inconsistencies. Run periodically or before major releases. Produces actionable findings with severity and file location

How do I install architecture-review?

Run the command: npx killer-skills add AJB-ajb/MeshIt/architecture-review. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for architecture-review?

Key use cases include: Automating code reviews for major releases or deploys, Debugging unexplained bugs by scanning for code inconsistencies, Periodically analyzing codebases for duplicated code and anti-patterns, Optimizing code complexity after merging parallel branches.

Which IDEs are compatible with architecture-review?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for architecture-review?

Requires access to relevant code files and directories. Specific to Next.js, Supabase, and SWR technologies. Needs periodic updates to rule sets for optimal issue detection.

architecture-review

Install architecture-review, an AI agent skill for AI agent workflows and automation. Review the use cases, limitations, and setup path before rollout.

SKILL.md

Readonly

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Supporting Evidence

Architecture Review

Name: architecture-review
Availability: InStock
Author: AJB-ajb

Codebase health check for Mesh. Detects duplicated code, anti-patterns, complexity, and inconsistencies across the Next.js + Supabase + SWR stack.

When to Run

Before major releases or deploys
After merging parallel branches
When debugging unexplained bugs
Periodically (weekly/biweekly)

How to Use

Read this file for the checklist and categories
For each category, scan the relevant files using the patterns described
Check individual rules/ files for detailed detection guidance
Report findings as: AREA > FILE(S) > SEVERITY > RECOMMENDATION

Review Checklist

1. Duplication (CRITICAL)

Scan for repeated code blocks that should be extracted to shared utilities.

Pattern	Where to check	Rule
JSON body parsing boilerplate	`src/app/api/**/route.ts`	`dup-json-parsing`
Provider identity checking	hooks + API routes	`dup-provider-check`
Record transformation logic	API routes returning DB rows	`dup-record-transform`

2. Error Handling (HIGH)

Pattern	Where to check	Rule
Fire-and-forget fetch calls	hooks, components	`err-fire-and-forget`
Silent `.catch(() => {})`	entire `src/`	`err-silent-catch`
Unhandled promise rejections	components with `.then()`	`err-unhandled-promise`
Inconsistent error response format	API routes	`err-response-format`

3. Supabase Client (HIGH)

Pattern	Where to check	Rule
Multiple client instances in one component	components with `createClient()`	`supa-client-instances`
Server/browser client confusion	hooks importing from wrong module	`supa-client-boundary`
Missing null checks after type casting	API routes with `as Record<>`	`supa-unsafe-cast`

4. SWR & Data Fetching (MEDIUM)

Pattern	Where to check	Rule
Missing revalidation after mutations	hooks with `.update()` or `.insert()`	`swr-missing-revalidate`
N+1 query patterns	hooks fetching per-item in loops	`swr-n-plus-one`
`select("*")` instead of specific columns	API routes + hooks	`perf-select-star`

5. Type Safety (MEDIUM)

Pattern	Where to check	Rule
Generic `Json` type for structured data	`src/lib/supabase/types.ts`, hooks	`type-generic-json`
Explicit `: any` usage	entire `src/`	`type-any`
Unsafe type assertions without validation	API routes, components	`type-unsafe-assert`

6. Component Structure (MEDIUM)

Pattern	Where to check	Rule
Components over 300 lines	`src/components/`	`comp-too-large`
Missing error boundaries	route layouts, dashboard	`comp-error-boundary`
Mixed fetch patterns (hook vs direct)	components	`comp-inconsistent-fetch`

Severity Guide

CRITICAL: Causes bugs, data loss, or security issues. Fix immediately.
HIGH: Creates maintenance burden or silent failures. Fix this sprint.
MEDIUM: Inconsistency or code smell. Fix when touching the file.
LOW: Style/preference. Fix opportunistically.

Output Format

## Architecture Review - [date]

### Findings

1. **[SEVERITY] [AREA]**: [description]
   - Files: [file paths with line numbers]
   - Recommendation: [what to do]

### Summary
- Critical: N
- High: N
- Medium: N
- Quick wins: [list easy fixes]

architecture-review — community architecture-review, MeshIt, community, ide skills

About this Skill

Killer-Skills Review

Core Value

Ideal Agent Persona

↓ Capabilities Granted for architecture-review

! Prerequisites & Limits

Source Boundary

Decide The Next Action Before You Keep Reading Repository Material

Start With Installation And Validation

Cross-Check Against Trusted Picks

Move To Workflow Collections For Team Rollout

Browser Sandbox Environment

⚡️ Ready to unleash?

FAQ & Installation Steps

? Frequently Asked Questions