| created | "2025-12-16T00:00:00.000Z" |
| modified | "2026-06-18T00:00:00.000Z" |
| reviewed | "2026-04-25T00:00:00.000Z" |
| allowed-tools | Read, Bash(git *), mcp__github__get_pull_request, mcp__github__list_issues, TodoWrite |
| args | [resource-name] [deployment-type] |
| argument-hint | [resource-name] [deployment-type] |
| disable-model-invocation | true |
| description | Generate deployment handoff docs — tech stack, access URLs, config, monitoring, dev checklist. Use when handing off a service, documenting deployments, or creating client-facing summaries. |
| name | deploy-handoff |
Deployment Handoff Command
Generate professional handoff messages for deployed resources and services with all necessary information for developer handoff.
When to Use This Skill
| Use this skill when... | Use deploy-release instead when... |
|---|
| Handing off an already-deployed service to another developer or client | Cutting a new release tag or driving release-please automation |
| Documenting deployment details (URLs, env vars, monitoring) on a ticket | Publishing a draft, pre-release, or manual GitHub release |
| Onboarding a new team member with access information for a running service | Setting up release-please-config.json / .release-please-manifest.json |
| Composing a client-facing deployment summary | Writing the Dockerfile (container-development) or Skaffold config (skaffold-orbstack) |
Context
- Git remotes: !
git remote -v
- Branch: !
git branch --show-current
- Last commit: !
git log --oneline --max-count=1
- README: !
find . -maxdepth 1 -name \'README.md\'
- Docker: !
find . -maxdepth 1 \( -name "Dockerfile" -o -name "docker-compose*.yml" \)
- CI/CD: !
find . -path '*/.github/workflows/*' -maxdepth 3 -name '*.yml'
- Config files: !
find . -maxdepth 1 \( -name ".env.example" -o -name "*.config.*" \)
Parameters
$1 (RESOURCE_NAME, optional): Name of the deployed resource/service
$2 (DEPLOYMENT_TYPE, optional): Type of deployment (web-app, api, database, infrastructure, etc.)
Execution
Execute this deployment handoff documentation workflow:
Step 1: Discover resource details
Gather deployment details from current repository context. Identify relevant documentation and configuration files. Extract repository information and branch details.
Step 2: Collect technical information
Collect:
- Service/resource name and purpose
- Deployment environment details
- Access URLs and endpoints
- Configuration and environment variables