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

Point it at a GitHub issue and get back a reviewed pull request. Hyperflow turns one AI coding session into a structured engineering pipeline: plan sharpens and decomposes the work, dispatch fans out parallel workers, and a domain specialist reviews every step — nothing ships unreviewed. 18 skills, 22 specialist reviewer and investigator agents, adaptive depth so a 5-line fix never triggers a deep run, and persistent per-project memory that lives in your repo and never leaves it. Runs on whatever model your session already uses — zero config, no API keys, no daemon. Works across Claude Code, Codex App/CLI, OpenCode, Grok, Antigravity, and Cursor.

ai agency v5.9.0
View Plugin

Installation

This skill is included in the hyperflow plugin:

/plugin install hyperflow@claude-code-plugins-plus

Click 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

  1. 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).
  1. Report the gate results in one short block (pass/fail per gate).
  2. 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).
  3. On Push: git push the branch (never --force to main/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.

Ready to use hyperflow?