river-review-security
セキュリティ観点の通常レビューエージェント。 基本的なセキュリティチェック、認証・認可設計、プライバシー設計の個別スキルへルーティングする。 repository / subsystem の明示的な security audit は river-review-security-audit へ委譲する。
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 1.6k
- Forks
- 490
01 前言 Front Matter
- id
- river-review-security
- name
- river-review-security
- tags
- [ "security", "entry", "routing" ]
- phase
- [ "midstream" ]
- applyTo
- [ "src/**/*.{ts,tsx,js,jsx,mjs}", "**/*.env*", "**/auth/**/*", "**/middleware/**/*" ]
- license
- MIT
- version
- 0.2.0
- category
- midstream
- severity
- critical
- outputKind
- [ "findings", "actions" ]
- description
- セキュリティ観点の通常レビューエージェント。 基本的なセキュリティチェック、認証・認可設計、プライバシー設計の個別スキルへルーティングする。 repository / subsystem の明示的な security audit は river-review-security-audit へ委譲する。
- inputContext
- [ "diff", "fullFile" ]
02 资源文件 1
- 参考文档references/ROUTING.md2.0 KB
03 SKILL.md 正文
Security Review(セキュリティレビュー)
セキュリティに影響する変更を検出し、適切な個別スキルで検証する。
When to Use / いつ使うか
- 認証・認可に関わるコード変更時
- 外部入力の処理ロジック変更時
- 機密データの取り扱い変更時
- セキュリティ関連の設定変更時
- 通常の PR / diff に対するセキュリティレビュー時
Security Audit Handoff
この skill は通常の diff-oriented security review を担当する。
ユーザーが repository-wide audit、subsystem audit、full security audit など、現在の diff を越える明示的な監査を要求した場合は river-review-security-audit へ委譲する。
PR / diff security review
-> river-review-security
repository / subsystem security audit
-> river-review-security-audit
単に「セキュリティ観点でレビュー」と指定された場合は本 skill を継続する。
security audit という語だけで full repository audit を推測しない。対象範囲が repository / subsystem / bounded source surface として明示されている場合だけ handoff する。
Routing / ルーティング
| キーワード | スキルID | 説明 |
|---|---|---|
| 脆弱性, XSS, SQLi, インジェクション | security-basic |
基本セキュリティチェック |
| プライバシー, 個人情報, GDPR | security-privacy-design |
プライバシー設計 |
| 認可, 権限, アクセス制御 | trust-boundaries-authz |
信頼境界・認可設計 |
デフォルト動作
- キーワード指定なし →
security-basicを実行 - セキュリティ関連ファイル(auth/, middleware/)→ 全スキル実行
Execution Flow / 実行フロー
0. 監査要求の判定
├─ 明示的な repository/subsystem audit → river-review-security-audit へ委譲
└─ 通常 PR/diff review → 以下を継続
1. 変更内容の分類
├─ 認証・認可コード → trust-boundaries-authz を優先
├─ データ処理コード → security-privacy-design を優先
└─ 一般コード → security-basic を実行
2. 各スキルの実行
├─ security-basic: OWASP Top 10チェック
├─ security-privacy-design: プライバシー影響分析
└─ trust-boundaries-authz: 認可モデル検証
3. 統合サマリの生成
Output Format / 出力形式
<file>:<line>: <message>
- Finding: 何が問題か(1文)
- Severity: critical / major / minor
- Impact: 何が困るか(短く)
- Fix: 次の一手(最小の修正案)
他スキルとの関係
river-review-security-audit は通常 diff review ではなく、明示的な repository / subsystem audit を担当する委譲先である。
| スキル | 関係 | 棲み分け |
|---|---|---|
adversarial-review (War Game) |
補完 | security は既知パターン検出、War Game は未知の攻撃経路発見 |
river-review-architecture |
補完 | security は「脆弱性」、architecture は「構造的安全性」 |
References
- ROUTING.md: 詳細なルーティングルール
04 同仓库更多 Skills
migrate-to-e2e
Moves an existing Playwright, Cypress, Selenium, Appium, Detox, Maestro, or TesterArmy suite to e2e one slice at a time, with the old suite running beside the new one until each ported test is proven. Keeps a MIGRATION.md progress file so any later session resumes where the last stopped. Optionally plants a defect to show both suites catch it. Use for /migrate-to-e2e, "migrate our tests to e2e", "port these Maestro flows", "move our TesterArmy tests", or when a project has an e2e config and an older suite still running.
e2e
Writes, runs, and debugs end-to-end tests for web and mobile apps with e2e, the agentic test runner, which mixes agent.act goals with exact locator assertions on a Playwright browser or an iOS or Android device. Also drives a project's running app live over the e2e MCP server to look at a screen, check a UI change, take a screenshot or record a video, and try a locator; and runs bug bashes, parallel e2e explore runs with each bug proven by a repro test. Use when a project depends on e2e or has an e2e.config.ts, when asked for end-to-end, browser, mobile, or agentic UI tests, to check a change in the running app, to QA or bug bash an app or branch, or when an e2e run fails.
create-verification-skill
Generate a project-local verify-<app> skill on top of e2e, so any coding agent can launch the app, check it is worth driving, exercise a feature the way a user does, keep evidence, and bug bash it. Writes the skill, a feature map with one explore charter per feature, and proves it once. Use for /create-verification-skill, "make a verification skill for this repo", or when a project has no scripted way to prove UI behavior.
deja-search
deja-vu memory — search the user's past AI coding sessions with the deja CLI. Holds what they already settled and never wrote into the repo (naming rules, banned or already-tried tools, required checks before merge, preferred values, who owns what). Use before your first edit in a task, before you call a change done or ready to merge, before you recommend a tool, library, design or reviewer, before re-debugging an error that may already be solved, when they say 'didn't we fix this before', 'what did we decide about X' or 'I already have that', and before telling them something on this machine does not exist.
deja-reflect
End-of-session reflection and memory curation with deja-vu. Review what was decided, what commands broke and what repaired them, and record durable project rules or decisions with deja remember so the next session starts with them.
revid
Make, edit, export and post AI videos with Revid (revid.ai) through the Revid MCP server. Use whenever the user wants a short-form or long-form video made (from an idea, a script, a URL, an article, a PDF, a tweet, a product page, their own clips, or a song), wants to find what is going viral on TikTok, YouTube, Instagram or X before making something, wants to edit or re-export an existing Revid project, generate a standalone AI image or clip, make a series episode, or publish and schedule a finished video to connected social accounts. Covers setup (hosted MCP with OAuth, or an API key), the 36 tools, credits, polling and the rules for publishing. Routes to the more specific revid-* skills when one fits.