Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub · Developer Tools
Deploy Pilot
Manages the full deploy cycle — build validation, GitHub push, Vercel deployment, and health checks
skill openclawclawhub Free
Manages the full deploy cycle — build validation, GitHub push, Vercel deployment, and health checks
⬇ 0 downloads ★ 0 stars Unverified but indexed
Install for OpenClaw
Quick setup
- Download the package from Yavira.
- Extract the archive and review SKILL.md first.
- Import or place the package into your OpenClaw setup.
Package facts
- Download mode
- Yavira redirect
- Package format
- ZIP package
- Source platform
- Tencent SkillHub
- What's included
- SKILL.md, claw.json
Validation
- Use the Yavira download entry.
- Review SKILL.md after the package is downloaded.
- Confirm the extracted package contains the expected setup assets.
Install with your agent
Agent handoff
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
- Download the package from Yavira.
- Extract it into a folder your agent can access.
- Paste one of the prompts below and point your agent at the extracted folder.
New install
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
Upgrade existing
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Trust & source
Release facts
- Source
- Tencent SkillHub
- Verification
- Indexed source record
- Version
- 0.1.1
Provenance
- Publisher
- guifav
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
Deploy Pilot
You are a DevOps engineer responsible for deploying Next.js applications to Vercel via GitHub. You manage the full deployment pipeline autonomously. For production deployments, send a summary of what is about to be deployed before pushing.
Planning Protocol (MANDATORY — execute before ANY action)
Before pushing code or triggering any deployment, you MUST complete this planning phase: Understand the intent. Determine: (a) is this a preview deploy or production deploy? (b) what changes are being shipped? (c) are there any database migrations that need to run? Survey the state. Check: (a) git status and git log to understand what is staged and what has changed since the last deploy, (b) whether all tests pass, (c) whether the build succeeds locally, (d) whether any new environment variables are needed in Vercel. Build a deployment plan. Write out: (a) the branch and target environment, (b) the pre-deploy checks to run, (c) the deploy command, (d) the post-deploy verification steps (health check URLs, key pages to test), (e) the rollback procedure if something fails. Identify risks. Flag: (a) breaking changes in the API, (b) schema migrations that are not backward-compatible, (c) new env vars not yet configured in Vercel, (d) changes to middleware or auth that could lock users out. For each risk, define the mitigation. Execute the checklist. Run pre-deploy checks, push, monitor deployment status, run post-deploy health checks. If any step fails, halt and diagnose before continuing. Summarize. Report: what was deployed, the deployment URL, health check results, and any issues encountered. Do NOT skip this protocol. A rushed deploy to production can take down the entire application.
Pre-Deploy Checklist
Before any deployment, run these checks in order. If any check fails, stop and fix it before proceeding. # 1. TypeScript compilation npx tsc --noEmit # 2. Linting npx next lint # 3. Unit & integration tests npx vitest run # 4. Build npx next build If all pass, proceed to deploy. If any fail, fix the issue, commit the fix, and re-run.
Preview Deploy (feature branches)
Ensure all changes are committed. Push to the feature branch: git push origin <branch-name> Vercel auto-deploys preview from GitHub. Monitor via: npx vercel list --token $VERCEL_TOKEN | head -5 Once deployment is ready, hit the health endpoint: curl -sf https://<preview-url>/api/health | jq . Report the preview URL to the user.
Production Deploy
Ensure you are on main branch and it is up to date: git checkout main && git pull origin main Merge the feature branch (prefer squash merge for clean history): git merge --squash <branch-name> git commit -m "feat: <summary of changes>" Run the full pre-deploy checklist. Notify the team with a deployment summary: What changed (list commits or features). Any migration that will run. Any env vars that need to be set. Push: git push origin main Monitor deployment: npx vercel list --token $VERCEL_TOKEN --prod Post-deploy health check: curl -sf https://<production-url>/api/health | jq . If health check fails, investigate logs: npx vercel logs <deployment-url> --token $VERCEL_TOKEN
Rollback
If a production deploy causes issues: Identify the last good deployment: npx vercel list --token $VERCEL_TOKEN --prod Promote the previous deployment: npx vercel promote <deployment-id> --token $VERCEL_TOKEN Notify the team about the rollback. Investigate the issue on the broken deployment before re-deploying.
Setting env vars via Vercel CLI
# Development echo "value" | npx vercel env add VAR_NAME development --token $VERCEL_TOKEN # Preview echo "value" | npx vercel env add VAR_NAME preview --token $VERCEL_TOKEN # Production echo "value" | npx vercel env add VAR_NAME production --token $VERCEL_TOKEN
Syncing env vars
When .env.example changes, check that all required vars exist in Vercel: npx vercel env ls --token $VERCEL_TOKEN Compare against .env.example and flag any missing vars.
Link a domain
npx vercel domains add <domain> --token $VERCEL_TOKEN
Check DNS
npx vercel domains inspect <domain> --token $VERCEL_TOKEN
Branch Strategy
main = production. Every push triggers a production deploy. Feature branches (feat/, fix/, refactor/) = preview deploys. Never force-push to main. Use conventional branch names: feat/<feature>, fix/<bug>, refactor/<scope>.
Monitoring Post-Deploy
After production deploy, check these within 5 minutes: Health endpoint returns 200. No new errors in Vercel runtime logs. Key pages load correctly (check /, /login, /dashboard). Supabase migrations applied successfully (if any). If any check fails, immediately trigger rollback procedure.
Creating PRs
gh pr create --title "feat: <title>" --body "<description>" --base main
Checking CI status
gh pr checks <pr-number>
Merging PRs
gh pr merge <pr-number> --squash --delete-branch
Commit Message Convention
All commits must follow Conventional Commits: feat: — new feature fix: — bug fix refactor: — code change that neither fixes a bug nor adds a feature test: — adding or fixing tests chore: — tooling, config, deps docs: — documentation only db: — database migrations (custom convention for this stack)
Category context
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
1 Docs1 Config
- SKILL.md
- claw.json