Skip to content
Back to skills

Review Leancode Arch

ASecurity

Review Flutter code against LeanCode architecture standards. Use when auditing a feature or folder for project structure, error handling, or logging.

  • 2 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added September 25, 2026
ai-agents

Security analysis

A100/100

Scanned September 25, 2026

npx -y skills add leancodepl/ai-plugins --skill review-leancode-arch --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Review Leancode Arch?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Review Leancode Arch
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/leancodepl-review-leancode-arch/badge)](https://www.skillsdirectory.com/skills/leancodepl-review-leancode-arch)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: review-leancode-arch
description: Review Flutter code against LeanCode architecture standards. Use when auditing a feature or folder for project structure, error handling, or logging.
argument-hint: "<feature-directory-or-file-path>"
---
# Review LeanCode Architecture

Review the specified feature or file against the architecture rules covered by this plugin.

## Checklist

### 1. Project Structure

- [ ] Feature has its own dedicated directory
- [ ] Feature follows the `features/<feature_name>` pattern
- [ ] Feature parts stay together; multi-page features use subdirectories
- [ ] No unnecessary cross-feature references
- [ ] Common code stays infrastructural and does not depend on features

### 2. Error Handling

- [ ] Failures are returned rather than thrown as exceptions
- [ ] Failure objects are defined as dedicated classes
- [ ] Error messages are precise and helpful
- [ ] Failing operations expose a retry path
- [ ] Network errors are handled separately
- [ ] Error UI uses reusable patterns rather than one-off implementations

### 3. Logging

- [ ] `logging/logging.dart` is used for logging
- [ ] Expected exceptions are caught and logged
- [ ] Important user and business-process traces are logged
- [ ] Sensitive data is not logged
- [ ] Frequent automatic actions are not logged

## Output Format

Group findings by domain. For each finding, include:

```
Location: <path>
Violation: <what is wrong>
Fix: <concrete suggestion>
```

If a finding really belongs to DI, navigation, analytics, localization, or state management, point to the matching dedicated plugin instead of forcing it into this review.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.