Hyperflow deploy
425 plugins, 2,810 skills, 200 agents for Claude Code. Open-source marketplace at tonsofskills.com with the ccpi CLI package manager.
npx -y skills add jeremylongshore/claude-code-plugins-plus-skills --skill hyperflow-deployAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
What its author says it does
Copied from the file, not written here
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.
SKILL.md
1.4 KB, as published. Nobody here has run it
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.