القائمة
Use when deciding between Foreman retry, reset, doctor --fix, worktree clean, abandon, or clean-state for failed/stuck/obsolete runs, branches, worktrees, or PRs.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when changing Foreman's Node/Pi worker bridge, detached worker config/env, Pi SDK sessions, custom tools, tool policy, observability, worker terminal events, or sandboxed Pi resource paths.
Use when a Foreman change may affect documentation, commands, workflows, prompts, setup, troubleshooting, operator expectations, or skill inventory/package behavior.
Use when changing Foreman's Elixir/OTP backend under packages/foreman_server: event store, projections, scheduler, run/phase actors, worker protocol, PR/VCS reconciliation, operations, auth, or storage/test isolation.
Use when a Foreman run appears stuck, has missing artifacts, stale projections, failed PR gates, confusing inbox/debug output, or potentially missing phase reports.
Use when changing Foreman's Git/Jujutsu support, VcsBackend abstraction, worktree/workspace handling, finalize/rebase/merge/push commands, or workflow/project VCS configuration.
Use when editing or diagnosing Foreman workflow YAML, bundled prompts, pipeline executor behavior, phase artifacts, retries, command/bash/builtin phases, PR gates, or stale runtime prompt/workflow copies.
| name | foreman-safe-recovery |
| description | Use when deciding between Foreman retry, reset, doctor --fix, worktree clean, abandon, or clean-state for failed/stuck/obsolete runs, branches, worktrees, or PRs. |
Use this skill for failed/stuck tasks, obsolete work, stale worktrees, retryable failures, branch cleanup, stale runtime assets, or operator cleanup.
foreman-pipeline-diagnosis order.foreman retry <task-id> --dispatch for understood retryable failures.foreman reset <task-id> --dry-run before reset; add --keep-worktree when preserving uncommitted investigation matters.foreman doctor --fix for safe automated stale prompt/workflow/skill/worktree checks/fixes.foreman worktree clean instead of manual rm -rf for stale worktrees.foreman abandon <task-id> for obsolete work that should not land.foreman clean-state --dry-run before --force for state cleanup.Record the task ID, run ID, failed phase, current status, root cause classification, command chosen, dry-run result, and reason string.