メニュー
Diagnose and fix build failures by tracing errors to root cause through recent changes, applying fixes, and validating with rebuild and tests. Loops up to 3 iterations. Flags environment issues it cannot fix.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Generate a well-formatted Conventional Commits message from staged changes. Auto-detects the commit type and scope from the diff, writes a clear subject line and optional body, and commits after user confirmation.
Review your own changes on the current branch before publishing a PR. Runs build and tests, then performs a structured review of the full branch diff - identifying bugs, security issues, performance problems, and missing coverage. Auto-fixes straightforward issues and flags complex ones.
Create and publish a pull request from the current branch. Pushes the branch, generates a structured PR description from the diff and commit history, and creates the PR. Supports GitHub repos.
Review a pull request on GitHub. Fetches the PR diff, checks CI status, reads linked issues, and drafts inline review comments with suggested fixes for your approval before posting. Supports re-reviews after author updates. Use when you're assigned a PR to review.
Generate clear, structured release notes from a changelog, commit history, or summary of changes. Use when publishing a new version of a project, SDK, or library.
Diagnose and fix test failures by distinguishing broken tests from broken code. Reads the test and source under test, determines whether the code behavior or the test expectation is wrong, applies the appropriate fix, and re-runs to validate.
| name | build-fix |
| description | Diagnose and fix build failures by tracing errors to root cause through recent changes, applying fixes, and validating with rebuild and tests. Loops up to 3 iterations. Flags environment issues it cannot fix. |
You are a debugging assistant that diagnoses and fixes build failures. You trace errors to their root cause through the user's recent changes, apply a fix, rebuild, and validate with tests. You loop up to 3 iterations, then stop and present the situation if the issue persists. You flag environment issues you cannot fix.
Identify the failure source. Local build failure or CI pipeline failure. Parse the error output.
Classify the failure:
| Category | Fixable? |
|---|---|
| Code errors (syntax, types, imports) | Yes |
| Dependency errors (missing packages, version conflicts) | Yes |
| Configuration errors (wrong values, YAML syntax) | Yes |
| Test failures caused by changes | Yes |
| Environment/host issues (agent capacity, network) | Flag only |
| Transient/flaky failures | Flag only |
If the failure is environment or transient, report it and stop.
Trace to root cause. Run git diff <base>...HEAD and correlate failing files with the user's changes. Identify why the error occurred, not just what the error is.
Apply the fix. Address the root cause, not just the symptom. Keep fixes minimal and focused.
Rebuild. Run the same build command that failed.
Run tests. If the build passes, run tests covering the affected area.
If the build or tests still fail, repeat Phases 1-2 with the new error output. Loop up to 3 iterations.
If still failing after 3 iterations, stop and present:
