deploy-staging
Skill2 starsChanged 6 months agoMITView on GitHub
Deploy to staging workflow — build, deploy to staging environment, run smoke tests, verify. Use after feature completion before production deployment.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- mosumoss/claude-harness-templatetheir own version, first seen Oct 20, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- mosumoss/claude-harness-template★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository40 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- ai-skillsSkill
- analyze-localSkill
- analyze-prodSkill
- analyzeSkill
- architectureSkill
- asset-validationSkill
- blog-postSkill
- bugfixSkill
- cloud-platformsSkill
- code-reviewSkill
- content-creationSkill
- context-engineeringSkill
- create-prSkill
- deployment-proceduresSkill
- deploy-productionSkill
- docsSkill
- feature-devSkill
- geo-writerSkill
- humanizerSkill
- infra-changeSkill
- marketing-operationsSkill
- marketingSkill
- ml-pipelineSkill
- planSkill
- pre-commitSkill
- productSkill
- project-initSkill
- prompt-engineeringSkill
- qaSkill
- releaseSkill
- run-testsSkill
- security-scanSkill
- seo-reviewSkill
- social-media-managerSkill
- test-localSkill
- test-strategySkill
- ui-ux-designSkill
- worktree-isolationSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 6 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 37
Read AGENTS.md and project config to determine:
- Distinctive: line 102
Follow platform-specific CLI or git-based deployment.
- Distinctive: line 120
Run critical path smoke tests:
- Distinctive: line 134
Check for errors, warnings, or unexpected behavior in the first 2–5 minutes.
- Distinctive: line 152
If all checks pass, suggest:
- Distinctive: line 153
Run full QA testing on staging
- Very specific: line 154
When ready: deploy-production skill
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Deploy to Staging
Structured workflow for deploying to staging environment. Builds the application, deploys, runs smoke tests, and verifies the deployment.
1. Pre-Deployment Checks
1a. Verify Branch State
// turbo
git branch --show-current// turbo
git status --short- Working directory must be clean
- Branch should be
mainor a release branch
1b. Run Tests
Invoke run-tests skill follow-up skill. All tests must pass before deploying.
1c. Identify Deployment Method
Read AGENTS.md and project config to determine:
| Signal | Method |
Dockerfile + K8s manifests | Container → Kubernetes |
Dockerfile + docker-compose | Container → Docker Compose |
| Helm charts | Container → Helm |
| Terraform | Infrastructure as Code |
| Serverless config (serverless.yml, SAM) | Serverless deployment |
| Static site (Next.js, Vite) | CDN / static hosting |
| Platform config (Netlify, Vercel, Railway) | Platform deployment |
2. Build
Build the application artifact:
| Stack | Command |
| Node.js | npm run build or pnpm build |
| Java | ./mvnw clean package -DskipTests |
| Python | docker build -t <image>:<tag> . |
| Go | go build -o bin/app ./cmd/api |
| .NET | dotnet publish -c Release |
Container Build (if applicable)
docker build -t <registry>/<image>:<tag> .Tag with git SHA or version:
docker tag <image> <registry>/<image>:<git-sha>3. Deploy to Staging
⚠️ Present deployment plan and request APPROVE before executing.
3a. Kubernetes / Helm
helm upgrade --install <release> <chart> \
-n staging \
-f values-staging.yaml \
--set image.tag=<tag> \
--dry-runAfter APPROVE:
helm upgrade --install <release> <chart> \
-n staging \
-f values-staging.yaml \
--set image.tag=<tag>3b. Docker Compose
docker compose -f docker-compose.staging.yml up -d3c. Platform (Netlify, Vercel, etc.)
Follow platform-specific CLI or git-based deployment.
4. Verify Deployment
4a. Health Check
// turbo
kubectl get pods -n staging -o wideOr curl health endpoint:
curl -s <staging-url>/health4b. Smoke Tests
Run critical path smoke tests:
- Application starts and responds
- Health endpoint returns 200
- Authentication flow works
- Core API endpoints respond correctly
- Database connectivity verified
4c. Monitor Logs
// turbo
kubectl logs -n staging -l app=<app-name> --tail=50Check for errors, warnings, or unexpected behavior in the first 2–5 minutes.
5. Summary
## Staging Deployment Summary
- **Version**: [version/tag]
- **Branch**: [branch name]
- **Environment**: staging
- **Method**: [K8s/Helm/Docker/Platform]
- **Build**: [success/fail]
- **Deploy**: [success/fail]
- **Health check**: [pass/fail]
- **Smoke tests**: [pass/fail]
- **Staging URL**: [url]
- **Next steps**: [QA testing / production deploy]If all checks pass, suggest:
- Run full QA testing on staging
- When ready:
deploy-productionskill
Integration
- Preceded by:
pre-commitskill,create-prskill (code ready) - Followed by:
deploy-productionskill - Roles:
devops-engineerrole,devops-architectrole (deployment strategy design)
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

