Skill2.4k repo starsupdated today

hyperflow-deploy

hyperflow-deploy executes a controlled release workflow by running pre-push validation gates (lint, typecheck, build, tests, and security checks) before prompting the user to confirm or hold a git push. Use this skill when the user signals readiness to ship code with language like "deploy," "release," or "push," ensuring no code reaches the remote repository without passing all checks and explicit approval.

View source Repository: claude-code-plugins-plus-skills

Install in Claude Code

Copy

git clone --depth 1 https://github.com/jeremylongshore/claude-code-plugins-plus-skills /tmp/hyperflow-deploy && cp -r /tmp/hyperflow-deploy/plugins/ai-agency/hyperflow/templates/antigravity/skills/hyperflow-deploy ~/.claude/skills/hyperflow-deploy

Then start a new Claude Code session; the skill loads automatically.

Definition

SKILL.md

# 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).
2. **Report** the gate results in one short block (pass/fail per gate).
3. **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).
4. 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.