القائمة
Use when working in this repo to load and maintain project expertise with the `mulch` CLI: session priming, recording learnings, searching conventions, and validating `.mulch/` records.
التثبيت باستخدام 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 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.
| name | mulch |
| description | Use when working in this repo to load and maintain project expertise with the `mulch` CLI: session priming, recording learnings, searching conventions, and validating `.mulch/` records. |
Mulch stores durable project expertise in .mulch/ so agents can reuse learned conventions, failures, decisions, patterns, guides, and references across sessions.
Run project priming before substantial repo work:
mulch prime
For work focused on specific domains or files, prefer narrower context:
mulch prime orchestrator cli
mulch prime --files src/orchestrator/pipeline-executor.ts
Use focused searches when investigating conventions or known failures:
mulch search "workflow yaml"
mulch query orchestrator
mulch query --all
mulch status
Before finishing meaningful work, decide whether anything should be preserved. Good candidates include repeated failures, non-obvious conventions, architecture decisions, reusable patterns, and troubleshooting guides.
mulch learn
mulch record <domain> --type <failure|convention|pattern|decision|reference|guide> --description "..."
Prefer existing Foreman domains when applicable, such as orchestrator, cli, dispatcher, planning, pipeline-executor, and epic-execution.
After changing .mulch/, verify the store:
mulch validate
mulch doctor
Use mulch sync only when explicitly preparing a commit that should include .mulch/ changes.