القائمة
Session-start ritual every agent on fleet-generator runs — read state, load context, report briefly, wait for direction.
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/bob-codedaptive/fleet-generator --skill bootstrapيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
Mandatory pre-commit checklist for Woodstock streams — scope check, identity check, test verification, anti-pattern detection, and the type(scope): description commit-message format.
Standard subagent flow for fleet-generator — when Woodstock spawns Snoopy for pre-flight, when to spawn Garfield for review, and when specialist reviewers (Dogbert, Cathy, Odie) get pulled in. Always-active doctrine.
Per-agent git commit identity for fleet-generator. Every agent signs commits so the human can scan git log and tell who did what.
عرض SKILL.md
| name | bootstrap |
| description | Session-start ritual every agent on fleet-generator runs — read state, load context, report briefly, wait for direction. |
| when_to_use | Starting a fresh agent session. Recovering after compaction. Asking what to read first. Subagent inheriting cwd from orchestrator. Trigger phrases: bootstrap, session start, run the bootstrap ritual, set cwd, what's in flight, where am I, getting started. |
| status | active |
| tags | ["skill"] |
| updated | 2026-05-07T00:00:00.000Z |
Every agent runs a startup ritual at the beginning of a session so that:
cd to the canonical working directory for this session. For
fleet-generator, the default is the repo root.
git pull --rebase origin <main-branch>
Skip pulls when working in a feature branch you don't want updated mid-session.
Read in this order:
CLAUDE.md — project rules and locked decisionsREADME.md — project overviewgit log --oneline -10 — what has been happening.claude/missions/ if a mission is in flightOne short paragraph (see the communication skill for verbosity).
Cover: current state, what changed recently, anything noticed. Do not
narrate the bootstrap steps. The human will ask follow-ups if needed.
Do not start working until told what to do. The exception: self-evident continuation of an in-flight mission with a clear next Part — proceed and report.
If part fails (can't pull, file missing, etc.), report the failure briefly and continue with what's available. Don't refuse to act because one step didn't complete.
Bootstrap is NOT skipped because:
The only legitimate skip: explicit human instruction.