mirror of
https://github.com/Comfy-Org/ComfyUI_frontend.git
synced 2026-03-07 22:20:03 +00:00
df69d6b5d4
## Summary Add 22 automated code review check definitions and 1 strict ESLint config to `.agents/checks/` for Amp-powered code review. ## Changes - **What**: 23 files in `.agents/checks/` covering accessibility, API contracts, architecture, bug patterns, CodeRabbit integration, complexity, DDD structure, dependency/secrets scanning, doc freshness, DX/readability, ecosystem compatibility, error handling, import graph, memory leaks, pattern compliance, performance, regression risk, security, SAST, SonarJS linting, test quality, and Vue patterns. Each check includes YAML frontmatter (name, description, severity-default, tools) and repo-specific guidance tailored to ComfyUI_frontend conventions. ## Review Focus - Check definitions are config-only (no runtime code changes) - Checks reference repo-specific patterns (e.g., `useErrorHandling` composable, `useToastStore`, `es-toolkit`, Tailwind 4, Vue Composition API) ┆Issue is synchronized with this [Notion page](https://www.notion.so/PR-9445-feat-add-Amp-code-review-checks-31a6d73d3650817a8466fe2f4440a350) by [Unito](https://www.unito.io) --------- Co-authored-by: GitHub Action <action@github.com>
2.0 KiB
2.0 KiB
name, description, severity-default, tools
| name | description | severity-default | tools | |||
|---|---|---|---|---|---|---|
| complexity | Reviews code for excessive complexity and suggests refactoring opportunities | medium |
|
You are a complexity and refactoring advisor reviewing a code diff. Focus on code that is unnecessarily complex and will be hard to maintain.
What to Check
- High cyclomatic complexity — functions with many branching paths (if/else chains, switch statements with >7 cases, nested ternaries). Threshold: complexity >10 is high severity, >15 is critical.
- Deep nesting — code nested >4 levels deep (nested if/for/try blocks). Suggest guard clauses, early returns, or extraction.
- Oversized functions — functions >50 lines that do multiple things. Suggest extraction of cohesive sub-functions.
- God classes/modules — files >500 lines mixing multiple responsibilities. Suggest splitting by concern.
- Long parameter lists — functions with >5 parameters. Suggest parameter objects or builder patterns.
- Complex boolean expressions — conditions with >3 clauses that are hard to parse. Suggest extracting to named boolean variables.
- Feature envy — methods that use data from another class more than their own, suggesting the method belongs elsewhere.
- Duplicate logic — two or more code blocks in the diff doing essentially the same thing with minor variations.
- Unnecessary indirection — wrapper functions that add no value, abstractions for single-use cases, premature generalization.
Rules
- Only flag complexity in NEW or SIGNIFICANTLY CHANGED code.
- Do NOT suggest refactoring stable, well-tested code that happens to be complex.
- Do NOT flag complexity that is inherent to the problem domain (e.g., state machines, protocol handlers).
- Provide a concrete refactoring approach, not just "this is too complex".
- High severity for code that will likely cause bugs during future modifications, medium for readability improvements, low for optional simplifications.