القائمة
Use when a Foreman change may affect documentation, commands, workflows, prompts, setup, troubleshooting, operator expectations, or skill inventory/package behavior.
التثبيت باستخدام 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 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 deciding between Foreman retry, reset, doctor --fix, worktree clean, abandon, or clean-state for failed/stuck/obsolete runs, branches, worktrees, or PRs.
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-doc-gate |
| description | Use when a Foreman change may affect documentation, commands, workflows, prompts, setup, troubleshooting, operator expectations, or skill inventory/package behavior. |
Use this skill for any fix/feature that changes behavior, commands/flags, workflows, prompts, setup, troubleshooting, operator expectations, runtime assets, or skill inventory.
README.md: user-facing overview, architecture, installation, feature bullets, quickstart.docs/user-guide.md: day-to-day operator workflows and expectations.docs/cli-reference.md: exact commands, flags, side effects, examples.docs/workflow-yaml-reference.md: workflow YAML schema, phase contracts, artifact/retry/PR behavior.docs/troubleshooting.md: failure modes, diagnosis, recovery, stale assets.docs/skill-integration.md: skill inventory, packaging, invocation, impact table.CLAUDE.md: project architecture/developer conventions when they change.AGENTS.md: repository-level agent instructions only when the agent operating policy itself changes.{{reportDir}}/DOCUMENTATION_REPORT.md; do not write it at repository root.docs/skill-integration.md, README.md, docs/user-guide.md, docs/cli-reference.md, and CLAUDE.md; leave AGENTS.md unchanged because no repository-level agent policy changes.