القائمة
After Fusebase Gate MCP tool sessions, produce a concise debug-oriented summary — what went smoothly, what did not, and actionable improvements to fusebase-gate skills, prompts, or MCP server behavior. Prioritize isolated SQL/NoSQL store flows.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use ONLY when the operator runs "/find-wasted-code" (or explicitly asks to "scan the repo for dead-end tool calls / broken links / missing helpers / footgun configs / silent push-through"). Statically scans THIS repo for friction footguns and writes a tracked report to docs/wasted-code/report.md. Manual-trigger ONLY — do NOT auto-invoke; the skill carries disable-model-invocation and no hook wires it. Read-only except the one report write. Findings are review candidates, never auto-fixes. Do NOT use for token/transcript economy (/token-waste-audit), for process ceremony (/find-wasted-effort), or for CLI/Flow drift health (/fusebase-health).
Use at Specify to classify a ticket Full vs Lightweight, and whenever a change looks small / reversible / low-risk ("small fix", "tweak", "hotfix", "drop pretty-printing", "bump a constant"). Operationalizes FR-21 — ceremony proportional to change size. Defines the eligibility gate, the change-note artifact, the one-pass build→verify→deploy procedure, and mid-flight promotion. Do NOT use for risky/uncertain work, schema/data migrations, security/permission changes, new public contracts needing a decision, unknown-root-cause diagnostics, or large features — those take the Full lane.
ALWAYS load at session start. After self-attesting, Read references/<role>.md for your role (Product Owner / AI Developer / Architect / Deploy phase) — role-specific don't-list, exact refusal phrasing for FR violations, and recovery pointers; shared cross-role protocols live in this file. Mandatory; not on-demand.
Use when the operator types /product-owner, asks to activate Product Owner, start a Product Owner or PO session, or searches /product in Codex for Fusebase Flow project management. Do NOT use for implementing code; route implementation to the AI Developer role.
Use when planning tasks that touch big source files, when an edit would push a file past the module-size ceiling, when the pre-commit module-size ratchet warns or blocks, or when generating policies/module-size-baseline.txt. Operationalizes FR-25 — module-size ratchet (ceiling default 800; over-ceiling files may shrink, never grow; extraction along a responsibility seam is in-scope, not scope creep). Do NOT use for docs/markdown size (FR-23 owns docs), to force decomposition of an existing monolith (that is its own explicit ticket), or to judge split quality by regex (seam-vs-mechanical is semantic — code-review owns it).
Use ONLY when verification passed AND operator explicitly says "prepare deploy" / "draft deploy" / "ship it"; drafts deploy handoff, captures deploy hash + probes + smoke, advises spec DRAFT→DONE flip. Do NOT auto-invoke; operator triggers explicitly.
| name | mcp-gate-debug |
| description | After Fusebase Gate MCP tool sessions, produce a concise debug-oriented summary — what went smoothly, what did not, and actionable improvements to fusebase-gate skills, prompts, or MCP server behavior. Prioritize isolated SQL/NoSQL store flows. |
Close the loop on Gate MCP work: turn friction into specific improvement ideas for:
.claude/skills/fusebase-gate/ (especially SKILL.md and references/*.md)After you finish (or pause) a coherent batch of Gate MCP tool_call operations — especially:
listIsolatedStores, createIsolatedStore, initIsolatedStoreStage, migration status/apply, row CRUD, queryIsolatedStoreSql, NoSQL equivalentsIf the user only asked a one-line question with no tools, skip this summary unless they ask for it.
Keep it scannable:
tools_describe, unclear errors, wrong orgId/storeId/stage, migration/drift confusion, permission surprises.fusebase-gate/references/isolated-sql-integrator-troubleshooting.md) or “MCP tool X description / prompt Y”When isolated-store tools were used, before proposing doc changes, re-read if needed:
.claude/skills/fusebase-gate/references/isolated-sql.md.claude/skills/fusebase-gate/references/isolated-sql-migration-discipline.md.claude/skills/fusebase-gate/references/isolated-sql-integrator-troubleshooting.md.claude/skills/fusebase-gate/references/isolated-nosql.md (if NoSQL)The summary should call out:
dryRun, checksum/version discipline).structuredIssues / drift messaging was understandable.project-template only, say so; if it belongs to the Gate MCP service or platform, label it as upstream.This skill is copied into the project only when the global CLI flag mcp-gate-debug is enabled (fusebase config set-flag mcp-gate-debug then fusebase update --skip-mcp --skip-deps --skip-cli-update --skip-commit).