context-review
Skill1 starsChanged 26 days agoMITView on GitHub
security-scan結果の曖昧な項目をユーザーに質問して確認する対話型レビュー。認証要否・エラー処理・データ露出・ビジネスロジックを選択肢形式で1問ずつ確認し、excluded/confirmed/needs_reviewに分類。「コンテキストレビュー」「context review」「誤検知を確認」「スキャン結果を確認したい」で起動。Do NOT use for 明確な誤検知の自動除外(false-positive-filter agent が担当、ユーザー起動不可)。
3 other projects use a version of this.
Adopted by
Most recently taken up by
- koukekoukej-glitch/context-engineertheir own version, first seen Oct 20, 2026
- dailyherold/skillstheir own version, first seen Oct 11, 2026
- JetBrains/contexttheir own version, first seen Sep 29, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- JetBrains/context★ 38same name
- dailyherold/skills★ 0same name
- koukekoukej-glitch/context-engineer★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository29 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- attack-reportSkill
- carefulSkill
- codify-insightSkill
- commitSkill
- cycle-retrospectiveSkill
- diagnoseSkill
- evolveSkill
- flask-qualitySkill
- flutter-qualitySkill
- generate-e2eSkill
- greenSkill
- hugo-qualitySkill
- js-qualitySkill
- learnSkill
- onboardSkill
- orchestrateSkill
- php-qualitySkill
- python-qualitySkill
- redSkill
- refactorSkill
- reviewSkill
- security-auditSkill
- security-scanSkill
- skill-makerSkill
- specSkill
- sync-skillsSkill
- ts-qualitySkill
The file
Files
Context Review
security-scan結果の曖昧な項目について、ユーザーに質問して確認する対話型スキル。
Usage
/context-review # 直近のsecurity-scan結果をレビュー
/context-review ./scan-result.json # 指定ファイルをレビューWorkflow
1. ANALYZE - security-scan結果を読み込み、曖昧な項目を抽出
2. QUESTION - 選択肢形式で1問ずつ確認
3. RESOLVE - 回答を反映して判定確定、JSON出力Question Categories
| Category | Description | 質問例 |
| auth-intent | 認証要否の意図確認 | 「このAPIは認証不要で正しいですか?」 |
| error-handling | 例外処理の妥当性 | 「本番環境でスタックトレースは無効ですか?」 |
| data-exposure | データ露出の意図確認 | 「このレスポンスに機密情報は含まれますか?」 |
| business-logic | ビジネスロジック検証 | 「この計算ロジックは仕様通りですか?」 |
Resolution Values
| Value | Meaning | 対応 |
| excluded | 意図的、脆弱性でない | レポートから除外 |
| confirmed | 脆弱性として確定 | レポートに含める |
| needs_review | 判断保留 | 手動レビュー推奨としてマーク |
Integration
/security-scan ./src # 1. スキャン実行
/context-review # 2. コンテキストレビュー(対話型)
/attack-report # 3. レポート生成With false-positive-filter
| スキル | 方式 | 対象 |
| false-positive-filter | パターンマッチ | 明確な誤検知 |
| context-review | ユーザー確認 | 曖昧な項目 |
Reference
詳細・質問テンプレート・出力JSON形式: reference.md
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

