القائمة
Start PyAutoLabs documentation, tutorial, notebook, example, or narrative-prose work through the Brain development workflow with the docs work type fixed.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Start-of-day wake-up routine for the PyAuto workspace — sync every repo to main and clean generated cruft (local), then a gh-API status glance (overnight scheduled-run conclusions, version-pin drift, resume context) plus /health and /hygiene, ending in one prioritized digest. Runs on the CLI and on mobile Claude Code chat / Codex (auto-skips local-only steps when there is no workspace). Use when starting the day or asked for a morning status/cleanup pass.
Coordinate PyAuto build, deploy, or release execution through the PyAutoBrain Build Agent, including its vitals consultation and PyAutoHands delegation. Use when the user asks to build, publish, deploy, or release.
Use the single PyAuto health door for readiness assessment, validation sweeps, active-work status, release-run status, or worktree status through the Brain and Heart-owned procedures.
Periodic hygiene sweep across PyAuto repos and worktrees — audit stale feature branches, tracking refs, stashes, and dirty checkouts, then execute per-bucket cleanups after confirmation. Use for end-of-week tidying or unwieldy branch lists.
Ship PyAutoLabs source-library changes — run tests, commit, push, open pending-release PRs, analyze downstream workspace impact, and update the issue and PyAutoMind task state.
Analyze how a mature PyAuto domain assistant should be reproduced as an exact clone, sibling, or seed through the PyAutoBrain Clone Agent, and birth a lightweight seed once a human has answered the clone-mode question. Use for assistant-cell cloning decisions and seed births.
| name | docs |
| description | Start PyAutoLabs documentation, tutorial, notebook, example, or narrative-prose work through the Brain development workflow with the docs work type fixed. |
Follow docs.md exactly. Route the task through start-dev; this is
a work-type entry, not a separate documentation conductor.
