flow-auto
Flow: Auto - Full Issue Lifecycle in One Shot - Complete end-to-end workflow: start worktree → analyze issue → ELI5 plan + necessity gate → implement ...
- License 许可
- MIT
- 所属仓库
- cooneycw/skillc
- 最近更新
- 2026-11-15
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- flow-auto
- description
- Flow: Auto - Full Issue Lifecycle in One Shot - Complete end-to-end workflow: start worktree → analyze issue → ELI5 plan + necessity gate → implement ...
02 资源文件 34
- 参考文档docs/agents/closing-report-contract.md7.4 KB
- 参考文档docs/agents/detector-contracts.md36.9 KB
- 参考文档docs/agents/flow-plan-record.md21.5 KB
- 参考文档docs/agents/issue-contract.md14.1 KB
- 参考文档docs/agents/knowledge-lifecycle.md6.6 KB
- 参考文档docs/decisions/0007-counter-model-review.md19.7 KB
- 参考文档docs/decisions/0008-instrument-negative-control-bound.md108.4 KB
- 参考文档docs/decisions/0009-oscillation-control.md10.5 KB
- 脚本lib/vendor.py42.0 KB
- 参考文档reference.md121.4 KB
- 脚本scripts/check-ignored-additions.sh8.9 KB
- 脚本scripts/codex-skill-resync.sh8.5 KB
- 脚本scripts/codex-skill-sync.py72.3 KB
- 脚本scripts/counter-model-receipt.py61.7 KB
- 脚本scripts/counter-model-reviewer-attribution.py20.1 KB
- 脚本scripts/eli5-vendor.py4.6 KB
- 脚本scripts/flow-ci-status.sh29.1 KB
- 脚本scripts/flow-driver-capability.sh27.3 KB
- 脚本scripts/flow-finish-gate.sh87.6 KB
- 脚本scripts/flow-live-driver-guard.sh7.3 KB
- 脚本scripts/flow-plan-record.py41.0 KB
- 脚本scripts/flow-stale-check.sh11.0 KB
- 脚本scripts/flow-start-resolve.sh39.9 KB
- 脚本scripts/flow-worktree-claim.sh24.3 KB
- 脚本scripts/flow-worktree-guard.sh21.2 KB
- 脚本scripts/friction-log.sh7.1 KB
- 脚本scripts/gate-lib.sh22.6 KB
- 脚本scripts/gh-pr-merge.sh106.6 KB
- 脚本scripts/hook-permission-census.sh20.6 KB
- 脚本scripts/nit-store-resolve.sh5.6 KB
- 脚本scripts/SHA256SUMS2.5 KB
- 脚本scripts/speckit-context.py31.9 KB
- 脚本scripts/stash-worktree-guard.sh25.1 KB
- 脚本scripts/worktree-remove.sh40.0 KB
03 SKILL.md 正文
<!-- GENERATED by claude-power-pack - scripts/codex-skill-sync.py; edit .claude/commands/flow/auto.md instead -->
Codex harness adaptations
Generated from a Claude Code command. Where the procedure references these Claude-only surfaces, adapt as follows:
- Native worktrees (
EnterWorktree/ExitWorktreetool calls,.claude/worktrees/paths): use plain git instead, with the worktree as a VISIBLE SIBLING of the repo -git worktree add ../<repo>-<branch> -b <branch>(or$FLOW_WORKTREE_BASE/<repo>-<branch>when that env var is set), work inside it, thengit worktree remove ../<repo>-<branch>when done. CLAUDE.mdreferences: readAGENTS.mdfirst - it is the Codex entry point. Where it defers toCLAUDE.md, follow that pointer andCLAUDE.mdis the rules; where it does not,AGENTS.mdis. Where the repository has noAGENTS.md, readCLAUDE.md.- Helper scripts referenced as
scripts/<name>are bundled underscripts/in this skill directory (byte-identical copies from the claude-power-pack checkout); some expect sibling repo resources, so prefer a full checkout when one is available. - Canonical guidance linked as
docs/<path>is bundled underdocs/in this skill directory (byte-identical copies from the claude-power-pack checkout). The source-relative../../../docs/...link in the command body resolves outside an installed skill, so the generated copy points at the bundled path instead. docs/ remains the only writable source. - Network: this skill's bundled helpers appear to call the network (
gh,git fetch/push,curl,aws, HTTP). Codex's workspace sandbox has no network, and an allow rule forghcovers only a top-levelghcommand, never one a helper runs. Run these helpers with escalated permissions. From inside the sandbox, "error connecting to api.github.com" means no network, not a GitHub outage or a bad login.
Flow: Auto - Full Issue Lifecycle in One Shot
Complete end-to-end workflow: start worktree → analyze issue → ELI5 plan + necessity gate → implement ...
Full procedure
Read reference.md in this skill directory for the complete, authoritative procedure before acting on this skill.
04 同仓库更多 Skills
tiny-check
Run the tiny project check
tiny-check
A synthetic gate selection fixture.
flow-check
Use when you are asked to run a project's quality checks (tests, lint, type checks, security scan): runs them in one step and reports what failed, without committing.
flow-check
Use when you are asked to run a project's quality checks (tests, lint, type checks, security scan): runs them in one step and reports what failed, without committing.
flow-check
Use when you are asked to run a project's quality checks (tests, lint, type checks, security scan): runs them in one step and reports what failed, without committing.
flow-check
Use when you are asked to run a project's quality checks (tests, lint, type checks, security scan): runs them in one step and reports what failed, without committing.