investigation-rules

Automate evidence-backed investigation reporting for debugging and defect analysis.

Updated Jan 30, 2026

Search Tags:#debugging #investigation #reporting #evidence #code-analysis #root-cause #db-analysis

Ready to run

npx skills add https://github.com/takemi-ohama/ai-plugins --skill investigation-rules

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: investigation-rules
Source: https://github.com/takemi-ohama/ai-plugins/tree/main/plugins/ndf/skills/investigation-rules
Command: npx skills add https://github.com/takemi-ohama/ai-plugins --skill investigation-rules

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

このルールは、調査・デバッグ・不具合レポート作成時のエビデンス重視の参照と整理を自動的に支援します。否定的結論のエビデンス要件や残課題の記載フォーマット、そしてハルシネーションを抑止するための裏取り原則を提供します。DB調査だけでなくコードベースの調査や仕様調査にも適用可能です。

Core Features & Use Cases

否定的結論には必ずエビデンスを添付するルール
残課題の記載フォーマットを標準化
裏取り原則でハルシネーションを防ぐ
レポートの品質保証と追跡性の向上

Quick Start

Use the investigation rules to produce a complete, evidence-backed report template for any defect or data anomaly.

Frequently Asked Questions about investigation-rules

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I create an evidence-backed debugging report for a DB investigation?▼

Use investigation rules to automate evidence-backed reporting for DB investigations and codebase reviews, enforcing structured evidence, traceability, and validation checks throughout your defect analysis.

What is the best way to prevent hallucination in root-cause analysis reports?▼

Prevent hallucination in root-cause analysis by applying explicit validation checks and cross-referencing principles that require data-backed conclusions and structured evidence for every negative finding.

How do I standardize remaining issues documentation in a defect analysis report?▼

Standardize remaining issues documentation by applying structured templates that enforce consistent formatting for unresolved questions, data-backed conclusions, and traceable evidence across your investigation.

Can I use this investigation reporting approach for codebase reviews and specifications?▼

Yes, this approach applies to codebase reviews and specifications, providing structured templates and validation checks to ensure data-backed conclusions and traceable evidence across multiple investigation types.

Why does my debugging report lack traceability for negative conclusions?▼

Debugging reports lack traceability when negative conclusions are not backed by structured evidence; enforcing explicit templates and validation checks ensures every conclusion includes required supporting data.