hashgraph-online/awesome-codex-plugins / plugins/alpoxdev/hypercore/skills/hyper-deploy
hyper-deploy
Flagged[Hyper] Use this skill when the user asks to deploy an app or service, set up a first deployment, change an existing deployment's configuration, diagnose and fix a failed or unhealthy deployment, or prove a repository is deploy-ready with lint, typecheck, and build checks - on Railway, Cloudflare, a Docker image, docker-compose, or a VPS. It detects the target from repository files, applies the matching target guide bundled in this skill, gates production, rollback, and data actions behind explicit approval, and saves a report under `.hyper/deploy/`. Do not use for application feature work, a CI workflow written with no deployment, or a deployment runbook written as a document.
references/report-template.md
View on GitHub# Report Template
Use this reference when writing `.hyper/deploy/<slug>/report.md`. Keep the `##` headings in English; write the prose in Korean.
## Template
```markdown
# <run title>
- Mode: preflight | setup | deploy | change | diagnose
- Target: <railway | cloudflare | docker-image | compose | vps> (<deciding file>)
- Identity: <project / environment / service, Worker and env, image repo:tag, or host and Compose project>
- Environment: <name> (production: yes | no)
- CLI: <binary> <version from --version>
- Result: ready | unproven | deployed | changed | fixed | exhausted | stopped-for-approval | blocked | handoff
## Evidence
- `<path>:<line>` - <what it shows>
- `<command>` -> <trimmed output, secrets redacted>
## Readiness
`PRE_DEPLOY_SUMMARY executed=<n> skipped=<m>` from `bash <skill-dir>/scripts/deploy-check.sh`, exit <code>. Skipped gates: <name - reason>.
## Actions
| # | Command | Tier | Result |
|---|---|---|---|
| 1 | `<command>` | proceed / named environment / approved | <state or output line> |
## Diagnosis
| Symptom | Log or state line | Cause | Fix | Before | After |
|---|---|---|---|---|---|
## Terminal State
- Deployment: <ID or version> -> <state>
- Health: <check and result>
- Runtime log window: <bounded window and fatal-error count>
## Proposed, Not Run
- `<exact command>` - <what it changes>, <what it does not restore>, <why it is proposed>
## Gaps And Risks
- <missing CLI, missing credential, `not run` checks, unresolved cause, volatile fact re-checked or not>
```
## Rules
- Omit a section only when the mode cannot produce it, and write `none` when it can but nothing happened.
- Every command in `## Actions` ran in this session.
- Redact tokens, secrets, and connection strings, and say what was redacted.
## Sources
> Checked 2026-11-07.
| Claim | Source |
|---|---|
| The report fields and the result values | this package's design, 2026-11-07 |
| A report that records what was tested, what was observed, and what was omitted | `instructions/harness-engineering/references/evidence-and-recovery.md` |
### Evidence grade
`LOCAL` - the template is this package's own.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 197k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |