القائمة
Use when a Beads coordinator needs to reconcile stale worker state, PR-review bookkeeping, or orphaned worktrees before dispatching new work.
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/Tzeusy/ai-bootstrap --skill beads-cleanupيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
عرض SKILL.md
| name | beads-cleanup |
| description | Use when a Beads coordinator needs to reconcile stale worker state, PR-review bookkeeping, or orphaned worktrees before dispatching new work. |
| metadata | {"owner":"tze","authors":["tze","OpenAI Codex"],"status":"active","last_reviewed":"2026-04-12"} |
| compatibility | Requires a Beads-backed git repository with `bd`, `git`, `gh`, `jq`, and git worktree support. Authenticated GitHub access is required for PR reconciliation and branch cleanup. |
Run this skill before a beads-coordinator loop when stale worker state may
have been left behind by crashes, compaction, out-of-token exits, or missed
handoffs.
This skill is a read-heavy reconciliation pass. It repairs Beads metadata and git artifacts; it does not implement code, dispatch workers, or invent new workflow rules.
beads-coordinator loopin_progress, blocked, pr-review, or review-running
stateThis skill is a routing layer over the existing Beads operating model.
../../../../../README.md../beads-coordinator/references/runtime-and-safety.md../beads-coordinator/references/coordinator-loop.md../beads-pr-reviewer-worker/SKILL.mdIf these sources disagree with this skill, fix this skill. Do not let cleanup become a competing doctrine.
assignee plus a fresh stall heartbeat, per
../beads-coordinator/references/runtime-and-safety.md.bd close / reopen / PR-driven label changes in response to a PR being
MERGED or CLOSED. It inspects PR state and reports the finding plus a
recommended action; the coordinator's Step 0 is the sole PR-state mutator.review-running lock release (a liveness repair, not PR-state
reconciliation — see Pass 5b/Pass 6 in local-state-reconciliation.md)..beads/dolt/ manually.../../references/token-efficiency.md): project
every bd/gh listing through jq to the fields the pass needs, batch
related checks into one composite command, and keep the final report to
findings and mutations — not raw command output.references/local-state-reconciliation.md
Load for stale in_progress claims, dependency unblocking, Dolt/worktree
health, and stale review-running labels.references/pr-review-reconciliation.md
Load for blocked original pr-review beads and blocked
pr-review-task review beads.references/reporting.md
Load for the cleanup report shape, rig-routing notes, command quick reference,
and final mutation summary.../beads-coordinator/references/runtime-and-safety.md if you need the
exact claim, stall-heartbeat, and mutation-authority rules before touching
Beads state.external_ref.references/reporting.md so the
coordinator has a clear mutation ledger before dispatch begins.Use for project-level engineering governance in any repository — bootstrap or audit the knowledge architecture (doctrine, specs, topology, standards), concretize a feature request into a spec delta, amend a spec found wrong mid-implementation, reconcile specs against implementation, run a repo-wide health audit, decide what to work on next via spec-driven planning, milestone synthesis, and doctrine-grounded feature ideation, or run a recurring vision-pursuit audit that generates the next best moves toward the project's ideal. Route to exactly one subskill per task. Triggers: "project shape", "bootstrap docs", "what should we work on next", "should we build this", "I want to add X", "spec this feature", "the spec is wrong", "break this down", "review this project", "audit the codebase", "does the code match the spec", "what's the next milestone", "brainstorm features", "run the vision pursuit", "relentlessly improve this project".
Use when analyzing or bootstrapping the five-pillar knowledge architecture of a software project: about/heart-and-soul (doctrine), about/legends-and-lore (RFCs/design contracts), about/lay-and-land (topology), about/craft-and-care (execution-quality standards), and openspec/ (capability specs at root). Use when: starting a new project's knowledge structure, auditing documentation health, onboarding, deciding where knowledge belongs, or mapping system topology. Triggers: "project shape", "bootstrap docs", "where should this go", "what's this project about", "project pillars", "heart and soul", "spec structure", "knowledge architecture", "system map", "topology", "lay of the land", "set up project structure".
Use for engineering-quality work on any change or codebase — holding an implementation or review to the engineering quality bar, code readability, test-suite rigor, module boundaries and dependency chains, diagnosing hard bugs and flaky failures to root cause, post-refactor cruft cleanup, codebase documentation, creating or reviewing skills against the skill quality bar, or Excalidraw diagrams. Route to exactly one subskill per subdomain; fan out subagents when a task spans several. Triggers: "hold this to the engineering bar", "is this code readable", "review these tests", "untangle these dependencies", "diagnose this", "flaky test", "clean up this refactor", "document this service", "audit the docs", "review this skill", "draw a diagram".
استنادا إلى تصنيف SOC المهني
