How do I install the Hyperflow Deploy skill?

Run npx skillmds@latest add jeremylongshore/hyperflow-deploy in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Hyperflow Deploy safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Hyperflow Deploy?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Hyperflow Deploy free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Hyperflow Deploy?

jeremylongshore (@jeremylongshore) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Hyperflow Deploy by jeremylongshore

Name: Hyperflow Deploy
Rating: 4.2 (5 reviews)
Author: jeremylongshore

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.

File contents

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 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.

Source: jeremylongshore/claude-code-plugins-plus-skills → plugins/ai-agency/hyperflow/templates/antigravity/skills/hyperflow-deploy/SKILL.md

Frequently asked questions