s977043/river-review - 2ページ

baseline-security-checks

Check common security risks in application code (SQLi, XSS, secrets).

原文の言語: 複数言語

supabase-rls-policy-review

Detects tables created without ROW LEVEL SECURITY enabled, over-permissive policies (USING (true) / WITH CHECK (true) without owner conditions), and service_role key exposure in client code.

suppression-feedback-workflow

Riverbed Memory の suppression entry を活用するときの判断基準と CLI 操作を案内する。

tailwind-css-class-hygiene-review

Checks Tailwind utility class hygiene at the syntax level: arbitrary-value overuse that bypasses the theme scale, conflicting/duplicate utilities on one element, and hardcoded arbitrary colors that should use design tokens.

type-driven-design-guard

Detect primitive obsession and missing domain/brand types; check that state is modeled via discriminated unions.

typescript-null-safety-guardrails

Enforce null/undefined safety for changed TypeScript code and suggest safer patterns.

typescript-strictness-guard

Enforce TypeScript strictness by reducing any/unsafe assertions and ensuring null handling.

vitest-mock-isolation-review

Detects Vitest test-isolation hazards: unrestored vi.spyOn/vi.mock without afterEach cleanup or restoreMocks config, un-awaited resolves/rejects assertions, and shared mutable module state across tests.

adr-decision-quality

Ensure ADRs capture context, decision, alternatives, tradeoffs, and follow-ups in a way that prevents future drift.

api-design-consistency

Ensure API design follows RESTful naming and consistent conventions.

api-versioning-backward-compatibility

Ensure API/contract changes specify versioning strategy, backward compatibility, deprecation plan, and migration guidance.

architecture-boundaries-dependencies

Ensure architecture/design docs define clear boundaries, ownership, dependency direction, and change impact to avoid tight coupling.

architecture-risks-assumptions-open-questions

Ensure design docs explicitly capture risks, assumptions, and open questions with owners, deadlines, and mitigation plans.

architecture-traceability-consistency

Ensure design changes stay consistent across ADRs, diagrams, and specs; decisions are traceable; and drift is explicitly managed.

architecture-validation-plan-guard

Detect missing validation plans (how to verify the design is correct) in design documents and ADRs.

原文の言語: 複数言語

cache-strategy-consistency-guard

Detect undefined or inconsistent cache strategies (layers, consistency, invalidation, TTL, failure handling) in design documents.

原文の言語: 複数言語

data-flow-state-ownership

Ensure designs define data flow, state ownership, consistency boundaries, and cross-boundary writes to prevent drift and incidents.

data-model-db-design-review

Ensure data model/DB designs cover constraints, integrity, indexes, migrations, rollback, and operational impacts.

event-driven-semantics-delivery-guarantees

Ensure event-driven designs specify delivery guarantees, ordering, idempotency, schema evolution, and replay/backfill strategy.

external-dependencies-vendor-risks

Ensure designs document third-party dependencies, SLAs, quotas, failure modes, and vendor lock-in mitigation.

failure-modes-observability-in-design

Ensure designs specify failure modes, timeouts, error contracts, and observability for critical flows.

laravel-migration-safety-review

Reviews Laravel migrations for destructive operations, change() dropping modifiers, locking index creation on large tables (PostgreSQL), and asymmetric down().

migration-rollout-rollback-plan

Ensure design/ADR changes include a concrete migration plan, rollout strategy, rollback conditions, and compatibility considerations.

migration-safety-review-framework-agnostic

スキーマ/データ移行の安全性を framework 非依存で審査する。破壊的スキーマ変更・ロック誘発・backfill・ロールバック可逆性・expand-contract の段階適用を、prisma / typeorm / Rails / Django / Alembic / 生 SQL などに横断適用する。

openapi-contract-completeness

Ensure OpenAPI specs define consistent request/response schemas, error model, auth, pagination, and backward compatibility.

operability-slo-runbook-readiness

Ensure designs define operability basics: SLO/SLI, monitoring, alerting, on-call actions, and incident handling expectations.

plangate-exec-conformance-guard

実装差分が plan / todo / test-cases アーティファクトの方針と一致しているかを検査し、逸脱・漏れ・意図外変更を検知する

pre-mortem

変更が将来インシデントや技術的負債を引き起こすと仮定し、その原因と経路を逆算して設計の盲点を可視化する

requirements-clarity-acceptance-criteria

Ensure requirement docs define scope, terminology, acceptance criteria, edge cases, and non-functional requirements.

security-privacy-design-review

Review data retention, deletion, backup residency, and cross-border data transfer.

原文の言語: 複数言語

trust-boundaries-authorization-architecture

Ensure designs define trust boundaries, authn/authz responsibilities, and propagation of identity/claims across services.

coverage-and-failure-path-gaps

Find missing tests for critical paths, edge cases, and failure handling in changed code.

test-presence-for-changed-code

Check whether changed code paths have corresponding tests and suggest minimal coverage.

component-variants-states-documentation

新規追加された UI コンポーネントに、variants（種類）とインタラクティブ状態（hover / focus / disabled / loading / error）が定義・文書化されているかを確認し、状態設計の欠落を検出する

cross-file-leakage-caller

モジュール/スキルの構造変更で当該ファイルは更新したが、caller 側が古い構造（旧参照・旧シグネチャ・旧採番）を参照したまま残るパターンを検出する

design-source-of-truth-conformance

リポジトリに DESIGN.md やデザイントークン定義が存在する場合に、新規 UI 実装の色・余白・フォントサイズ・角丸・シャドウがその定義済みスケールに準拠しているかを照合する。定義が無ければ実行しない

end-to-end-wiring

宣言した処理（計測 / 通知 / 保存 / 検証 / 例外通知）が起点から末端まで途切れず配線されているかを確認し、「実装したつもり」で経路が途中で止まっている欠落を検出する

refactor-claim-audit

コミット/PR の「全部置換した」「-N%削減」等の完了主張を grep で反証できる残骸や best/typical/worst 試算で検証し、抽出・集約リファクタでは並列度(Promise.all)/fast-path/遅延評価の性能特性退行と、Map/Set 集約キーの cross-kind 衝突による検出漏れも監査する

review-automation-boundary-guard

Detect review findings that belong in CI/lint/formatter rather than human review.

self-contradiction-detector

同一ファイル/隣接ファイル内で「規則Xを守れ」と宣言した直後にXを破っている、宣言と実装の乖離を検出する