Skip to content

notque/vexjoy-agent / skills/review/review

Code review: systematic single-file, parallel multi-reviewer, full-repo audit, PR diff review.

FileKindSize
SKILL.mdskill md11.7 KB
references/architecture-smell-baseline.mdmarkdown6.8 KB
references/audit-playbook.mdmarkdown10.2 KB
references/disprove-pass.mdmarkdown2.3 KB
references/go-review-patterns.mdmarkdown4.0 KB
references/receiving-feedback.mdmarkdown3.0 KB
references/report-template.mdmarkdown1.9 KB
references/reviewer-code.mdmarkdown6.2 KB
references/reviewer-code/code-quality.mdmarkdown4.6 KB
references/reviewer-code/comments.mdmarkdown3.6 KB
references/reviewer-code/config-safety.mdmarkdown3.7 KB
references/reviewer-code/dead-code.mdmarkdown3.2 KB
references/reviewer-code/language-checks.mdmarkdown6.7 KB
references/reviewer-code/language-specialist.mdmarkdown4.7 KB
references/reviewer-code/naming.mdmarkdown3.3 KB
references/reviewer-code/performance.mdmarkdown3.5 KB
references/reviewer-code/simplifier.mdmarkdown5.3 KB
references/reviewer-code/test-analyzer.mdmarkdown4.5 KB
references/reviewer-code/type-design.mdmarkdown4.0 KB
references/reviewer-domain.mdmarkdown9.1 KB
references/reviewer-domain/adr-compliance.mdmarkdown3.0 KB
references/reviewer-domain/business-logic.mdmarkdown4.6 KB
references/reviewer-domain/common-bugs.mdmarkdown6.7 KB
references/reviewer-domain/edge-case-tables.mdmarkdown4.5 KB
references/reviewer-domain/operational-preferred-patterns.mdmarkdown7.2 KB
references/reviewer-domain/pragmatic-builder.mdmarkdown4.2 KB
references/reviewer-domain/production-gaps.mdmarkdown5.3 KB
references/reviewer-domain/sapcc-structural.mdmarkdown5.4 KB
references/reviewer-domain/state-machine-verification.mdmarkdown5.2 KB
references/reviewer-domain/structural-categories.mdmarkdown5.8 KB
references/reviewer-perspectives.mdmarkdown8.0 KB
references/reviewer-perspectives/clarity-and-assumption-detection.mdmarkdown4.8 KB
references/reviewer-perspectives/code-review-detection.mdmarkdown4.4 KB
references/reviewer-perspectives/contrarian.mdmarkdown2.3 KB
references/reviewer-perspectives/meta-process.mdmarkdown2.7 KB
references/reviewer-perspectives/newcomer.mdmarkdown2.0 KB
references/reviewer-perspectives/pedant.mdmarkdown3.3 KB
references/reviewer-perspectives/review-detection-commands.mdmarkdown8.7 KB
references/reviewer-perspectives/skeptical-senior.mdmarkdown2.9 KB
references/reviewer-perspectives/user-advocate.mdmarkdown2.9 KB
references/reviewer-system.mdmarkdown14.0 KB
references/reviewer-system/api-contract.mdmarkdown3.4 KB
references/reviewer-system/compliance-checklists.mdmarkdown5.1 KB
references/reviewer-system/concurrency.mdmarkdown3.6 KB
references/reviewer-system/dependency-audit.mdmarkdown3.3 KB
references/reviewer-system/docs-validator.mdmarkdown4.0 KB
references/reviewer-system/error-messages.mdmarkdown3.1 KB
references/reviewer-system/financial-resilience-de-eu.mdmarkdown5.3 KB
references/reviewer-system/german-it-security.mdmarkdown10.7 KB
references/reviewer-system/industry-specific-compliance.mdmarkdown3.5 KB
references/reviewer-system/migration-safety.mdmarkdown3.3 KB
references/reviewer-system/observability.mdmarkdown3.1 KB
references/reviewer-system/security-authz.mdmarkdown9.0 KB
references/reviewer-system/security-ci-cd.mdmarkdown7.6 KB
references/reviewer-system/security-data-exfil.mdmarkdown9.5 KB
references/reviewer-system/security-finding-template.mdmarkdown3.0 KB
references/reviewer-system/security-injection.mdmarkdown6.3 KB
references/reviewer-system/security-pii.mdmarkdown7.3 KB
references/reviewer-system/security.mdmarkdown3.6 KB
references/reviewer-system/silent-failures.mdmarkdown3.6 KB
references/reviewer-system/sovereign-cloud-data-residency.mdmarkdown6.6 KB
references/reviewer-system/stride-threat-model.mdmarkdown3.2 KB

references/reviewer-code/language-checks.md

View on GitHub
# Language-Specific Checks Catalog

Complete check catalogs for Go, Python, and TypeScript. Load after detecting the language from file extensions.

## Go (when reviewing .go files)

**Modern stdlib (Go 1.21+, Go 1.22+)**:
- `slices.SortFunc` instead of `sort.Slice`
- `slices.Contains` instead of manual loop search
- `strings.CutPrefix`/`strings.CutSuffix` instead of `HasPrefix`+`TrimPrefix`
- `min`/`max` builtins instead of custom helpers (Go 1.21+)
- `for range N` loop syntax (Go 1.22+)
- Loop variable capture fix (Go 1.22+): flag `v := v` or `item := item` inside `for range` loops — these are unnecessary since Go 1.22 and are an LLM tell
- Loop variable capture fix (Go 1.22+): flag `go func(x Type) { ... }(x)` capture patterns — since Go 1.22, loop variables are per-iteration so the closure argument is unnecessary
- `maps.Clone`, `maps.Keys` instead of manual map operations
- `log/slog` instead of `log.Printf` for structured logging

**Go idioms**:
- Error wrapping with `%w` and checking with `errors.Is`/`errors.As`
- Receiver type consistency (all pointer or all value, not mixed)
- Package naming conventions (lowercase, single-word, no underscores)
- Unexported types with exported constructors (`NewFoo()`)
- Blank identifier only with explicit justification

**Concurrency**:
- Goroutine leaks: goroutines without shutdown path
- Context cancellation: functions accepting `context.Context` must respect cancellation
- Mutex per resource, not per struct (fine-grained locking)
- `sync.Once` for initialization, not `init()` with flags
- Channel direction in function signatures

**Resources**:
- `defer Close()` must come AFTER the error check on the open call
- Connection pool sharing (reuse shared clients across requests)
- `http.DefaultClient` reuse vs creating new clients
- File descriptor limits awareness

**Failure modes**:
- Premature interface abstraction (interface with one implementation)
- Over-engineered error types (custom error types for simple errors)
- Unnecessary channels when a mutex suffices
- `init()` for non-trivial work (side effects, I/O, network calls)
- Returning concrete types but accepting interfaces at boundaries
- `MockXxx` types in production (non-test) files — test doubles belong in `_test.go` files
- Creating separate `*sql.DB` connection pools when a shared pool should be injected

**LLM tells**:
- Functional options pattern on types with 2-3 fields (a simple struct literal suffices)
- Table-driven tests everywhere, even for single-case scenarios
- Excessive interface segregation (one-method interfaces for everything)
- Config validation layers with reflection when a simple `if` works
- Overly verbose error messages repeating the function name
- Builder pattern for structs with few fields
- Loop variable shadowing (`v := v`) in Go 1.22+ projects — LLMs trained on older Go generate this
- `defer rows.Close()` without checking `rows.Err()` after the iteration loop — LLMs miss the error check
- Verbose `if err != nil { return fmt.Errorf("failed to X: %w", err) }` wrapping errors that already have good context (e.g., `strconv.ParseUint` already says what it was parsing)

## Python (when reviewing .py files)

**Modern Python (3.10+, 3.11+, 3.12+)**:
- Walrus operator `:=` for assignment expressions in conditions
- `match` statement for structural pattern matching (3.10+)
- `type` statement for type aliases (3.12+)
- `tomllib` for TOML parsing (3.11+)
- `TaskGroup` for structured concurrency (3.11+)
- `ExceptionGroup` and `except*` syntax (3.11+)
- Generic syntax `def foo[T](x: T)` (3.12+)

**Python idioms**:
- List/dict/set comprehensions over `map`/`filter` with lambdas
- Context managers (`with`) for resource management
- Generators and `yield` for large dataset processing
- `pathlib.Path` over `os.path` for path manipulation
- `collections.defaultdict` over manual key-existence checks
- F-strings over `format()` or `%` formatting
- `dataclasses` or `attrs` over manual `__init__` boilerplate

**Concurrency**:
- `asyncio` patterns: proper `async with`, `async for`
- `TaskGroup` structured concurrency over `gather` with manual cancellation
- Proper cleanup in async context managers
- Thread safety when mixing sync and async code

**Resources**:
- Context managers (`with`) for file handles, connections, locks
- `atexit` handlers for global cleanup
- Signal handling for graceful shutdown
- `contextlib.suppress` over empty except blocks

**Failure modes**:
- Mutable default arguments (`def foo(items=[])`)
- Bare `except:` or `except Exception:` without re-raise
- `import *` polluting namespace
- Global mutable state
- Monkey patching in production code
- String concatenation in loops (use `join`)

**LLM tells**:
- Overly verbose type hints on obvious types (`x: int = 5` when `x = 5` is clear)
- Unnecessary docstrings on self-documenting simple functions
- Java-style getter/setter methods instead of properties or direct access
- Abstract base classes for single implementations
- Excessive use of `typing.Optional` when `| None` syntax exists (3.10+)
- Over-engineered class hierarchies for simple data transformations

## TypeScript (when reviewing .ts/.tsx files)

**Modern TypeScript (5.0+, 5.2+)**:
- `satisfies` operator for type checking without widening
- `const` type parameters for literal type inference
- `using` declarations for resource management (5.2+)
- Template literal types for string pattern types
- `NoInfer<T>` utility type (5.4+)

**TypeScript idioms**:
- Discriminated unions over type casting for type narrowing
- `Zod` or similar for runtime validation matching TypeScript types
- Proper generic constraints (`extends`) over `any`
- Mapped types and conditional types for type-level programming
- `as const` for literal type inference

**React (when reviewing .tsx)**:
- React 19 patterns: no `forwardRef` (ref is a regular prop), `useActionState`, `useOptimistic`
- Proper hook dependency arrays (exhaustive deps)
- `memo` only with measured performance justification
- Server Components vs Client Components distinction
- Use framework data loading instead of `useEffect` for data fetching

**Failure modes**:
- `any` overuse instead of proper types or `unknown`
- Type assertions (`as`) over type narrowing with guards
- Barrel file bloat causing circular dependencies
- Circular dependencies between modules
- Enum overuse when union types suffice
- `namespace` in modern code

**LLM tells**:
- Overly abstract factory patterns for simple object creation
- Unnecessary class-based components in modern React
- Redundant null checks when TypeScript strict mode already narrows
- Over-engineered dependency injection frameworks
- Excessive abstraction layers (repository pattern wrapping simple fetch calls)
- Generic utility types that reimplement built-in ones
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall