AgentStack
SKILL verified MIT Self-run

Hyperflow Deploy

skill-jeremylongshore-claude-code-plugins-plus-skills-hyperflow-deploy · by jeremylongshore

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.

No reviews yet
0 installs
3 views
0.0% view→install

Install

$ agentstack add skill-jeremylongshore-claude-code-plugins-plus-skills-hyperflow-deploy

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Hyperflow Deploy? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

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.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.