From container-plugin
Generates professional handoff documentation for deployed resources/services by gathering git repo details, configs, Docker files, CI/CD workflows, URLs, and access info. Useful post-deployment for developer transitions.
npx claudepluginhub laurigates/claude-plugins --plugin container-pluginThis skill uses the workspace's default tool permissions.
Generate professional handoff messages for deployed resources and services with all necessary information for developer handoff.
Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.
Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.
Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.
Generate professional handoff messages for deployed resources and services with all necessary information for developer handoff.
git remote -vgit branch --show-currentgit log --oneline --max-count=1find . -maxdepth 1 -name \'README.md\'find . -maxdepth 1 \( -name "Dockerfile" -o -name "docker-compose*.yml" \)find .github/workflows -maxdepth 1 -name '*.yml'find . -maxdepth 1 \( -name ".env.example" -o -name "*.config.*" \)$1 (RESOURCE_NAME, optional): Name of the deployed resource/service$2 (DEPLOYMENT_TYPE, optional): Type of deployment (web-app, api, database, infrastructure, etc.)Execute this deployment handoff documentation workflow:
Gather deployment details from current repository context. Identify relevant documentation and configuration files. Extract repository information and branch details.
Collect:
Find and compile:
Assemble:
Create a professionally formatted handoff message with clear sections, action items for the receiving developer, and contact information for follow-up questions.
The command generates a structured message with:
format: markdown # slack, email, markdown
include_sensitive: false # Include sensitive config info
detail_level: standard # minimal, standard, comprehensive
template_style: professional # professional, technical, brief
.env files and configuration# Basic handoff for current project
claude chat --file ~/.claude/skills/deploy-handoff/SKILL.md
# Specific service handoff
claude chat --file ~/.claude/skills/deploy-handoff/SKILL.md "User API" "web-service"
# Comprehensive handoff with full details
claude chat --file ~/.claude/skills/deploy-handoff/SKILL.md "Payment System" "microservice" --detail-level comprehensive
## ๐ Deployment Handoff: [Service Name]
**Service**: [Service Name]
**Environment**: [Production/Staging/Development]
**Deployment Date**: [Date]
**Deployed By**: [Developer Name]
### ๐ Service Overview
- **Purpose**: [Brief description of functionality]
- **Technology Stack**: [Languages/frameworks used]
- **Status**: โ
Active and operational
### ๐ Access Information
- **Service URL**: [Primary access point]
- **Admin Dashboard**: [Management interface]
- **API Documentation**: [API docs location]
- **Health Check**: [Monitoring endpoint]
### ๐ Documentation & Resources
- **Repository**: [GitHub repository URL]
- **Branch/Tag**: [Deployed version]
- **Setup Guide**: [Configuration instructions]
- **Troubleshooting**: [Known issues and solutions]
### โ
Developer Handoff Checklist
- [ ] Review service functionality and purpose
- [ ] Access all provided URLs and interfaces
- [ ] Verify monitoring and alerting setup
- [ ] Test basic functionality
- [ ] Review configuration and environment variables
### ๐ Support & Contact
For questions or issues with this deployment, please:
1. Check the troubleshooting guide first
2. Review logs at [log location]
3. Contact [deployer] for immediate assistance
*Generated on [date] for [project/client]*