Menu
Diagnose flow workflow setup and environment
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Flow: Auto - Full Issue Lifecycle in One Shot - Complete end-to-end workflow: start worktree → analyze issue → ELI5 plan + necessity gate → implement ...
Run quality checks (lint + test + typecheck + security) without committing
Flow: Finish - Quality Gates, Commit, Push, and Create PR - Run quality checks, commit changes, push the branch, and create a pull request.
Flow Commands - Streamlined worktree-based development workflow. No locks, no Redis - just git.
Flow: Merge PR and Clean Up - Merge the current branch's PR, then clean up the worktree and branch.
Install the flow helper family into ~/.claude/scripts/ (fixes exit-127 on marketplace-only installs)
| name | flow-doctor |
| description | Diagnose flow workflow setup and environment |
Generated from a Claude Code command. Where the procedure references these Claude-only surfaces, adapt as follows:
EnterWorktree/ExitWorktree tool calls, .claude/worktrees/ paths): use plain git instead - git worktree add <path> -b <branch>, work inside it, then git worktree remove <path> when done.~/.codex/config.toml, or fall back to the referenced repo scripts and CLI entry points.CLAUDE.md references: Codex reads AGENTS.md; treat them as the target repo's agent-context file.scripts/<name> are bundled under scripts/ 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.Diagnose flow workflow setup and environment
Read reference.md in this skill directory for the complete, authoritative procedure before acting on this skill.