メニュー
Run production-readiness checks for revert.wtf packages, catalog data, MCP server, frontend, Docker/Coolify deployment, docs, and generated artifacts.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Run evidence-locked enrichment passes over existing revert.wtf catalog errors, preserving good entries while improving generic explanations, actions, references, and helper metadata.
Use revert.wtf safely from agents, tools, browsers, or integrations through bounded HTTP APIs, MCP tools, and lightweight package subpaths without downloading the full catalog into client bundles.
Add or update precise revert.wtf catalog entries, fixtures, source metadata, and matcher tests for one or a small set of EVM/RPC/provider/wallet/protocol errors.
Perform broader source-backed catalog enrichment for new EVM ecosystems, protocols, providers, standards, or deprecated/renamed/sunsetting coverage.
Work on the revert.wtf Next.js frontend as a distinctive error-forensics product surface, not a generic SaaS or stock brutalist page.
Maintain or use the read-only revert.wtf MCP server that exposes bounded catalog search, parser, selector lookup, AA explanations, x402 entries, and Blockscout registry tools to agents.
| name | revertwtf-release-readiness |
| description | Run production-readiness checks for revert.wtf packages, catalog data, MCP server, frontend, Docker/Coolify deployment, docs, and generated artifacts. |
| version | 0.1.0 |
Use this skill before production, launch, partner demos, Coolify deployment, package publishing, or major handoff.
node scripts/build-catalog-data.mjs --generate --dist --check
node --experimental-strip-types scripts/validate-catalog.ts
node scripts/check-catalog-duplicates.mjs --fail-on=id,same-source-selector
node node_modules/typescript/bin/tsc -p packages/core/tsconfig.json --noEmit
node node_modules/typescript/bin/tsc -p packages/catalog/tsconfig.json --noEmit
node node_modules/typescript/bin/tsc -p packages/selectors/tsconfig.json --noEmit
node node_modules/typescript/bin/tsc -p packages/parser/tsconfig.json --noEmit
node node_modules/typescript/bin/tsc -p packages/aa/tsconfig.json --noEmit
node node_modules/typescript/bin/tsc -p packages/client/tsconfig.json --noEmit
node node_modules/typescript/bin/tsc -p packages/search/tsconfig.json --noEmit
node node_modules/typescript/bin/tsc -p packages/cli/tsconfig.json --noEmit
node node_modules/typescript/bin/tsc -p packages/mcp/tsconfig.json --noEmit
node node_modules/typescript/bin/tsc -p apps/web/tsconfig.json --noEmit
pnpm --filter @revertwtf/catalog test
pnpm --filter @revertwtf/parser test
pnpm --filter @revertwtf/aa test
pnpm --filter @revertwtf/cli test
pnpm --filter @revertwtf/mcp test
0.1.0 until the first npm release.license, repository, homepage, bugs, files, and the correct exports or bin surface.Dockerfile should copy every package package.json needed for dependency installation./errors..dockerignore should keep caches, node_modules, dist, docs, fixtures, and local metadata out of the image.On this Windows workspace, recursive pnpm scripts, Vitest, Next dev/build, or child-process stdio MCP smokes can fail with spawn EPERM. Do not hide that. Use direct tsc, in-memory MCP tests, and bounded smoke checks, then report which process-spawn checks were blocked.
Summarize: