一键导入
build-failure-analysis
Analyze build failures to identify root causes and provide fix instructions. Do not use for deployment failures or runtime errors.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Analyze build failures to identify root causes and provide fix instructions. Do not use for deployment failures or runtime errors.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use to implement a REST or GraphQL API endpoint from a specification or description, including request validation, error handling, and accompanying tests. Activate for building a new API route, resolver, or handler end-to-end. Do NOT use for API design/contract creation, documentation generation, or frontend API consumption.
Use to implement background job processing with a queue, worker, retry with exponential backoff, dead letter queue, and monitoring. Activate when the request involves offloading work from the request cycle (emails, reports, data processing). Do NOT use for real-time event streaming, webhook handling, or scheduled cron jobs.
Use to scaffold a new project from scratch — generating directory structure, configuration files, entry points, and a README skeleton. Activate when starting a new project, service, or package and needing a production-ready starting point. Do NOT use for adding features to existing projects, generating tests, or CI/CD configuration.
Use to design and implement a caching layer for data that is expensive to compute or fetch. Activate for cache-aside, write-through, or write-behind patterns, TTL strategy, and cache invalidation logic. Do NOT use for database query optimization, CDN configuration, or HTTP response caching headers.
Use to generate a CI/CD pipeline configuration for building, testing, and deploying an application. Activate for GitHub Actions, GitLab CI, CircleCI, or similar pipeline tools for any tech stack. Do NOT use for infrastructure provisioning, Dockerfile creation, or deployment strategy design.
Use to generate production-ready code for a new feature, function, class, or module from a description. Activate for writing new code from scratch with error handling, inline documentation, and a self-review checklist. Do NOT use for refactoring existing code, code review, or test generation.
| name | build-failure-analysis |
| description | Analyze build failures to identify root causes and provide fix instructions. Do not use for deployment failures or runtime errors. |
| version | 1.1.0 |
| time_saved | Manual: 30–90 minutes | With skill: 5–15 minutes |
| license | Proprietary — Personal Use Only |
| category | debugging |
| complexity | Intermediate |
| tokens | ~3000 |
| tags | ["build","compilation","bundler","ci","debugging"] |
| author | vheins |
Identify root causes of build/compilation failures and provide exact fix steps and clean build procedures.
| Variable | Type | Req | Description |
|---|---|---|---|
tech_stack | string | Yes | Build tool and language |
build_output | string | Yes | Full error logs |
context | string | Yes | Recent changes (code, deps, CI) |
rm -rf node_modules && install).| Case | Strategy |
|---|---|
| No Logs | Provide verbose commands; list common causes/diagnostics. |
| CI vs Local | Check version diffs, env vars, and case-sensitive pathing. |
| OOM | Provide memory config (JVM/Node) or incremental build steps. |
flowchart TD
A([Start: Build Failure Analysis]) --> B[Parse tech_stack, build_output, context]
B --> C{Build output available?}
C -- No --> D[Provide verbose build command]
D --> E[List common failure causes]
E --> F[Suggest clean build procedure]
C -- Yes --> G[Classify Build Failure Type]
G --> H{Failure type?}
H -- Compilation --> I[Identify root file/line, ignore cascading]
H -- Missing dep --> J[Check package install, verify resolution]
H -- Config --> K[Validate config syntax]
H -- Environment --> L[Check runtime version/tools]
H -- OOM --> M[Increase heap size / chunk build]
H -- Circular dep --> N[Map import cycle, break reference]
I & J & K & L & M & N --> O[Provide exact fix steps]
O --> P{Fails in CI only?}
P -- Yes --> Q[Identify env diff, fix both]
P -- No --> R[Provide clean build sequence]
Q --> R
R --> S([Output: 5-Section Report])
@upstash/context7-mcp: Library documentation and examples.@modelcontextprotocol/server-sequential-thinking: Complex reasoning.| Version | Date | Description |
|---|---|---|
| 1.1.0 | 2026-03-20 | Restructured: examples/references separated, added fields |
| 1.0.0 | 2026-03-20 | Initial release |