hyperflow-deploy
Hyperflow ship phase. Use when the user is ready to release — verbs like ship, push, release, deploy, "cut a release", "ready to push". Runs pre-push gates (lint + typecheck + build + tests + security sweep), then asks before pushing. Never --no-verify, never force-push to main.
Allowed Tools
No tools specified
Provided by Plugin
hyperflow
Fifteen specialized slash commands turn one Claude session into a structured multi-agent engineering pipeline. Thinking models orchestrate, triage, and review; worker models execute in parallel — every step is a Worker → Reviewer pair, and every non-trivial phase fans into sub-phases with their own reviewers. Auto-routing is on by default — say 'audit the diff', 'debug this test', 'large migration', or 'run a workflow' and the orchestrator routes to the right skill without the /hyperflow:* prefix. /hyperflow:workflow uses Claude Code dynamic workflows for big tasks and a portable Codex/OpenCode adapter where native workflows are unavailable; /hyperflow:spec asks the questions a senior engineer would; /hyperflow:scope decomposes into a batched task graph; /hyperflow:dispatch fans out persona-stitched workers under tiered review; /hyperflow:amplify rewrites a rough prompt into a high-quality one before you run it. 15 composable personas, 6 adaptive flow profiles, and persistent project memory compound across sessions. Works across Codex App/CLI, Claude Code, OpenCode, and Antigravity.
Installation
This skill is included in the hyperflow plugin:
/plugin install hyperflow@claude-code-plugins-plusClick to copy
Instructions
hyperflow-deploy — ship phase (Antigravity single-agent)
Gate, then ship. Follow the hyperflow doctrine. Pushing is always an explicit, confirmed step.
Steps
- Pre-push gates — run in order, fix or halt on failure:
- lint · typecheck · build · tests · a quick security sweep (no secrets in the diff, no blocked files committed).
- Report the gate results in one short block (pass/fail per gate).
- Push gate via AskUserQuestion — binary
Push / Hold(no recommended marker). State the branch, ahead/behind vs the remote, and any caveat (e.g. red gate from someone else's files). - On Push:
git pushthe branch (never--forcetomain/master). On Hold: leave commits local and say so.
Hard rules
- Never
git push --no-verify. If a pre-push hook fails — even on files you don't own — surface it and hold; do not bypass. - Never force-push to
main/master. - If a gate is red because of a concurrent session's uncommitted/untracked files, report that the push is held on external failure — your commits stay clean and local until the tree is green.