菜单
Default entry point for PyAutoLabs development tasks — implement, fix, add, change, refactor, migrate, optimize, document, test, ship, or open a PR — even when the user does not say start_dev. Not for pure questions, reviews, status checks, or explicit workflow opt-outs.
用 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 | start-dev |
| description | Default entry point for PyAutoLabs development tasks — implement, fix, add, change, refactor, migrate, optimize, document, test, ship, or open a PR — even when the user does not say start_dev. Not for pure questions, reviews, status checks, or explicit workflow opt-outs. |
Follow start_dev.md in this directory exactly — the
authoritative workflow body. reference.md holds the long-form templates and
the branch survey; shared context and cross-harness notes are in
../WORKFLOW.md. Do not duplicate or reinterpret the
workflow here — if it changes, edit start_dev.md.
