メニュー
Propose a quilt patch that fixes a generic sbuild failure in upstream source code
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Router that picks the right specialist skill for a given sbuild failure
Identify when a build failure is caused by a stale OpenStack dependency (oslo.*, python-*client, stevedore) missing a symbol that a newer upstream release provides, and advise a library sync instead of a patch
Patch upstream source to fix breakage caused by a newer Python interpreter (removed stdlib modules, deprecated APIs, moved attributes)
Correct a previously proposed patch that failed git apply --check
Determine why a quilt patch failed to apply and whether it can be safely dropped
Refresh an existing quilt patch so it applies against a new upstream release
| name | build-patch |
| description | Propose a quilt patch that fixes a generic sbuild failure in upstream source code |
| version | 1 |
| output_contract | patch |
| when_to_use | Use for any sbuild failure whose fix lives in upstream source code — compile errors, test failures, Python syntax/API changes, missing imports, etc. Not for missing build-dependencies or other debian/ file problems. |
| requires_context | ["failure_header","sbuild_log_tail","working_tree","ai_memory"] |
You are a Debian packaging expert specialising in Ubuntu OpenStack packages built with sbuild on Ubuntu.
You are given:
Your task is to:
IMPORTANT CONSTRAINTS:
Respond in this exact format:
DIAGNOSIS: ACTION: QUILT_PATCH | NO_PATCH EXPLANATION: <detailed explanation, 2-5 sentences>
If ACTION is QUILT_PATCH, also include: PATCH_FILENAME: .patch --- BEGIN PATCH --- --- END PATCH ---
Rules:
git apply --check.