القائمة
Deprecated shim — build failures are now handled inline by the active execution/debugging workflow; do not route here
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Run a regression-tests-first, smell-by-smell deslop/refactor workflow that preserves behavior and raises signal quality. Use when the user asks to "cleanup", "refactor", "deslop", or when follow-up code has duplicates, dead code, weak boundaries, or fallback-like slop.
Run read-only deep repository analysis and return a ranked synthesis with explicit confidence, concrete file references, and clear evidence-vs-inference boundaries. Use when a user says "analyze", "investigate", "why does", "what's causing", or needs grounded cross-file explanation before any changes are proposed.
Deprecated compatibility shim for Claude advisor requests. Use `ask` with the claude backend instead.
Deprecated compatibility shim for Gemini advisor requests. Use `ask` with the gemini backend instead.
Ask a locally installed external advisor CLI (Claude or Gemini) for focused questions, reviews, brainstorming, or second opinions, and capture a reusable artifact. Use when the user wants a Claude/Gemini second opinion, "ask claude", or "ask gemini".
Strict autonomous delivery loop that runs deep-interview, ralplan, ultragoal, code-review, and ultraqa in order with automatic re-planning when gates are not clean. Use on "autopilot", "autonomous", "build me", "create me", "make me", "full auto", "handle it all", or "I want a/an…".
| name | build-fix |
| category | build |
| status | deprecated |
| description | Deprecated shim — build failures are now handled inline by the active execution/debugging workflow; do not route here |
| agent_created | true |
| triggers | ["build fix","fix build","build-fix"] |
Ported from oh-my-codex
build-fix. OMX runtime conventions ($macroinvocation,omxCLI,.omx/state directory) are replaced with WorkBuddy idioms (Skill tool, Agent tool, task list,.workbuddy/memory).
Hard-deprecated. Do not invoke or route this skill.
Build failures should be handled by the active execution, debugging, or verification
workflow (e.g. run the build, read the error, fix the offending code, re-run). There is
no separate persistent "build-fix" mode in WorkBuddy — repair happens inline as part of
normal task progress, tracked with the task list and .workbuddy/memory.
If you arrived here from an old reference, just fix the build directly in the current session.
