deploy

Generates deployment checklists and executes branch-based deployments with post-deploy smoke tests.

1|Updated Jun 21, 2026
One-click install
npx skills add https://github.com/tapway/shogun-os --skill deploy-tapway
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deploy
Source: https://github.com/tapway/shogun-os/tree/main/skills/software-development/deploy
Command: npx skills add https://github.com/tapway/shogun-os --skill deploy-tapway

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Deploying to staging or production without a structured process leads to broken releases, zombie server processes, and undetected failures in API, database, or auth layers. This Skill enforces a repeatable deployment pipeline with verification at every stage. ## Core Features & Use Cases - Pre-Deployment Verification: Runs tests, lint checks, and git status validation before any deployment proceeds. - Branch-Based Routing: Maps develop branch pushes to staging and main branch merges to production via CI auto-deploy. - Post-Deploy Smoke Testing: Verifies port listening, API endpoints, Supabase connectivity, and auth middleware redirects after each deploy. - Rollback & WSL Pitfall Handling: Provides git revert rollback steps and documents WSL-specific issues like zombie next-server processes that survive shell exit. - Use Case: After merging a feature into develop, use this Skill to confirm the staging deploy succeeded by checking that port 3000 is listening, the tasks API returns data, and unauthenticated users are redirected to the login page. ## Quick Start Ask the agent to deploy the current project to staging and run the full post-deploy verification including API, Supabase, and auth checks.

Frequently Asked Questions about deploy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy a Next.js app to staging and production safely?

Push to the develop branch for staging or merge develop into main for production, both triggering CI auto-deploy. Before deploying, verify all tests pass, lint is clean, and the git working tree has no uncommitted changes.

How to run post-deploy smoke tests on a Next.js server?

Check that the port is listening with ss -tlnp, curl API endpoints like /api/tasks to confirm data returns, and verify the homepage returns a 307 redirect to /login for unauthenticated users. Also check server logs for ready or error messages.

Why does my Next.js server port stay occupied after the process exits?

On WSL, a background next-server child process can outlive the shell that spawned it, keeping the port claimed. Find the PID with ss -tlnp and kill it with kill -9, since lsof may return empty even while the port is in use.

How do I roll back a failed deployment in git?

Run git revert HEAD followed by git push to undo the last commit and trigger a redeploy of the previous state. This works for both staging and production branches that auto-deploy via CI.

When should I not use this deployment workflow?

Do not use it for local development, where running the dev server directly is sufficient, or for version bumping and code review, which belong to release and code review workflows. It is designed for staging and production deployments only.