agentleFS
Sign inStart free
ZAidBinAsifZAidBinAsif/flutter-ai-starter/.cursor/skills/review-code/SKILL.md

review-code

Skill0 starsChanged 5 months agoMITView on GitHub

Structured code review before merge or when user asks for review

69 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use audit-test-suite, change-data-safely and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • yaohuangguanSkill

    audit-test-suite

    Find where an existing test suite is weak and decide what to test next, ranked by risk. Use this when asked to add missing tests, find gaps, raise coverage, assess test quality or see which areas are thin, even if the request only mentions a coverage percentage.

    Also in 3 projects that use this

  • yaohuangguanSkill

    change-data-safely

    Change a database schema or stored data without breaking running code or losing data. Use this for any migration, new or changed column, backfill, bulk update, delete, index, or change to a stored format, including in small projects. Data mistakes are often impossible to undo.

    Also in 3 projects that use this

  • mrdulasolutionsSkill

    clear-caches

    Clear extension caches, analysis data, and drafts from the database. Use when testing sender lookups, analysis, or draft generation from a clean state.

    Also in 3 projects that use this

  • GeiserXSkill

    docs-loop

    Use when the user asks to audit docs, check documentation for stale claims, or verify docs against the code.

    Also in 3 projects that use this

  • mrdulasolutionsSkill

    electron-devtools-testing

    Test the Electron app interactively using Chrome DevTools Protocol. Use when the user asks to test, verify, or interact with the running app via browser automation.

    Also in 3 projects that use this

  • GeiserXSkill

    full-loop

    Drive a repository to done with sergio-loop, then keep improving it with refine-loop at a descending theta. Use only when the user explicitly invokes full-loop.

    Also in 3 projects that use this

  • +1 more from mrdulasolutions
  • +4 more from GeiserX
  • +1 more from yaohuangguan

The file

Create a free account to mount
Files
SKILL.md

Code review

Review against repo rules. Verify claims with evidence — do not speculate.

Checklist

Architecture & layering

  • Feature-first layout; no cross-feature imports
  • Views observe ViewModels only — no direct repository/network calls
  • Repositories return Result<T, Failure>; errors mapped, not leaked raw
  • DI via MultiProvider / route providers — no globals or static singletons
  • go_router + refreshListenable for auth if applicable

State & UI

  • ChangeNotifier ViewModels; notifyListeners after state changes
  • _disposed guard after async in ViewModels (not mounted)
  • No business logic in build; setState only for ephemeral local UI
  • Design tokens used; l10n for user strings; touch ≥48dp / ≥44pt

Security & privacy

  • No secrets in source; tokens in secure storage
  • No client AI SDK calls; RLS on new Supabase tables
  • No PII in logs/analytics

Tests (required)

  • Every changed code unit has matching tests per testing.mdc
  • Fakes for ViewModels; Mockito only at I/O boundaries
  • Design-system: widget + golden (light + dark) if touched

Quality

  • Minimal diff; no drive-by refactors
  • flutter analyze --fatal-infos and flutter test would pass
  • Stack changes documented in docs/DECISIONS.md

Output format

## Summary
<1–2 sentences>

## Blockers
- ...

## Suggestions
- ...

## Verified OK
- ...

High-stakes changes

Auth, payments, migrations: recommend doubt-review before merge.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free