メニュー
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.
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.
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.
| name | cross-repo-impact |
| description | 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. |
| license | MIT |
| allowed-tools | ["file-search","mcp__github__authenticate"] |
Cross-repository contract analysis skill.
contracts/For each changed shared surface, search other repos for consumers (GitHub MCP search). List each consumer with file:line. Assess whether consumer breaks silently or loudly.
If breaking change is unavoidable:
Option A: Versioned endpoint (API v2 alongside v1) ← preferred (constitution Article III)
Option B: Dual-write period (produce both old and new shape)
Option C: Feature flag (new shape only for flagged users)
{
"changed_surface": ["POST /api/v1/reservations request body"],
"breaking": true,
"downstream_consumers": [
{ "repo": "azoom-carparking-qr-code", "file": "src/api/reservation.ts", "line": 23 }
],
"recommended_strategy": "versioned_endpoint",
"migration_effort": "medium"
}
Article III (API Versioning) applies to all cross-repo contract changes. Reviewer must flag any change that modifies a live endpoint without version bump as HIGH finding.