القائمة
Initialize a local git repository and create an initial commit for an aflow lifecycle bootstrap. Operates local-only, writes only README.md, and emits AFLOW_STOP for ambiguous or failed states.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | aflow-init-repo |
| description | Initialize a local git repository and create an initial commit for an aflow lifecycle bootstrap. Operates local-only, writes only README.md, and emits AFLOW_STOP for ambiguous or failed states. |
Use this skill only when the aflow engine invokes it as the pre-lifecycle repo bootstrap handoff. The engine supplies the repo root, branch name, README title, and README body in the prompt. Do not invoke this skill manually unless replicating the engine's exact handoff call.
git fetch, git pull, git push, or any command that contacts a remote. Do not add, remove, or configure remotes.README.md. Do not stage or commit any other pre-existing files.AFLOW_STOP: repository already has commits — bootstrap must not rewrite history and stop immediately.main_branch is empty or unset in the prompt, emit AFLOW_STOP: main_branch is required for repo bootstrap..git/ exists in the repo root:
.git/ directory: run git init -b <main_branch> to initialize a new repository. Configure git user identity: check git config user.email and git config user.name; if either is empty, set them to "aflow-bootstrap@local" and "aflow bootstrap" respectively..git/ exists but HEAD points to a different unborn branch: run git symbolic-ref HEAD refs/heads/<main_branch> to repoint HEAD to the correct branch without creating a commit. Do not use git checkout -b, which fails on an unborn branch with no commits..git/ exists and HEAD already points to <main_branch> as an unborn branch: no branch setup is needed, proceed to the next step.git rev-parse --verify HEAD. If it succeeds (exit code 0), emit AFLOW_STOP: repository already has commits — bootstrap must not rewrite history.README.md in the repo root with the provided title and body. The format is:
# <readme_title>
<readme_body>
README.md already exists, overwrite it — the engine has already verified zero commits so no user history is lost.README.md:
git add README.md
git commit -m "Initial commit"
git rev-parse --verify HEAD must succeed.git symbolic-ref --short HEAD must equal <main_branch>.git init fails for any reason.git add README.md fails.git commit fails (e.g., no identity configured and auto-config above did not help).main_branch, readme_title, or readme_body).Emit AFLOW_STOP: <reason> on its own line. The engine detects this and fails the run immediately.
Checkpoint-scoped execution for an existing AFlow plan. Use when an agent should implement exactly one checkpoint, verify it, synchronize plan state, and then stop instead of continuing into the next checkpoint.
Lightweight execution reinforcement for an existing AFlow plan. Use when an agent must resume from the first unchecked checkpoint and keep the plan synchronized with verified progress.
Create a strict AFlow checkpoint handoff plan for coding work that will be implemented by another model, tool, or later session. Use when the user explicitly wants the aflow pattern or a checkpoint-based handoff plan.
Checkpoint-scoped review for AFlow plans. Use when an agent should review the latest checkpoint attempt, compare it against the original plan, and either approve that checkpoint or create a focused fix plan for that checkpoint only.
Final no-squash review for a completed checkpointed AFlow handoff. Use when the original plan is complete and the reviewer must either approve the whole result or create one focused follow-up fix plan.
Review a completed autonomous AFlow plan, compare the full accumulated implementation against the original plan, and either squash the whole handoff into one final commit or create a focused fix plan for the remaining failed checkpoints or behaviors.