القائمة
Root cause analysis for bugs, incidents, and regressions. Produces a structured RCA with reproduction steps, impact assessment, and recommended minimum fix. Used in bug-triage and hotfix patterns.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Six-dimension structured code review framework. Produces severity-ranked findings (CRITICAL/HIGH/MEDIUM/LOW/INFO) with evidence mapped to AC IDs, and a verdict (APPROVE/REQUEST_CHANGES/NEEDS_DISCUSSION). Used by kopi-reviewer agent.
Playwright-based evidence capture protocol. Produces screenshot + HTML + console proof mapped per AC ID. Used by kopi-validate agent to generate pass/fail evidence for the evidence-manifest.
Converts a Figma frame into a structured intent-package with AC confidence scoring, state matrix enumeration, and JP/VI/EN annotation handling. Used by kopi-figspec agent.
Knowledge harvesting — surface, distil, store, and recall tacit business knowledge. Run the Recall → Codebase-first → Grill → Distil → Confirm loop when a task needs a business fact that is not written down (why "予約" is always "reservation", when a feedback is a CR vs a Bug, which flow touches payments). Invokable by kopi-brse, kopi-implement, and any kopi agent that hits a business-knowledge gap. Writes verified facts to knowledge/.
Assemble accumulated project knowledge + context into a compact, reusable context-pack — for the orchestrator to hand to subagents on fan-out (so each subagent does NOT re-gather), or for any agent/member to re-establish context fast on resume. Complements `harvest` (harvest distils NEW tacit facts into knowledge/; context-pack packages EXISTING context — code, knowledge, glossary, structure). Reads knowledge/INDEX.md + glossary + structural signals; never invents new knowledge.
Cross-repository contract analysis. Identifies downstream impact of changes to shared types, API contracts, or shared utilities. Used by kopi-reviewer in cross-repo pattern and when breaking changes are detected.
| name | investigate |
| description | Root cause analysis for bugs, incidents, and regressions. Produces a structured RCA with reproduction steps, impact assessment, and recommended minimum fix. Used in bug-triage and hotfix patterns. |
| license | MIT |
| allowed-tools | ["file-search","mcp__github__authenticate"] |
Root cause analysis skill for bugs, incidents, and regressions.
Read the bug report. Identify minimum reproduction case. Capture: exact steps, environment, expected vs. actual behavior. Check if reproducible in current main branch.
git bisect if regression. Add targeted logging. Narrow scope to specific file:line range.
| Category | Description |
|---|---|
logic_error | Wrong conditional, off-by-one, incorrect algorithm |
race_condition | Async timing issue, shared state |
missing_validation | Input not validated at boundary |
api_contract_drift | BE/FE contract mismatch |
dependency_change | Library update broke behavior |
config_error | Wrong env var, misconfigured flag |
data_issue | Unexpected data in prod not handled |
Which users are affected? Is data corrupted or just display wrong? Is there a workaround? Is this a security issue? (→ escalate to kopi-guard immediately)
{
"task_id": "...",
"root_cause": "logic_error",
"affected_file": "src/auth/token.ts",
"affected_line_range": "L42-L67",
"reproduction_steps": ["..."],
"impact": { "scope": "all users", "data_corrupted": false },
"recommended_fix": "...",
"escalate_to_guard": false
}