Agent skill · Data & Analytics

deploying-to-staging-environment

Use when deploying changes to staging across relay, relay-dashboard, and relay-cloud repos - coordinates multi-repo branch syncing using git worktrees, automatically triggers staging deployments via GitHub Actions

AgentWorkforcegithub.com/AgentWorkforceGitHub ↗
claude-codeApache-2.0
Install
npx skills add AgentWorkforce/relay --skill deploying-to-staging-environment --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 13 KB
Bundled scripts: none
Path: .claude/skills/deploying-to-staging-environment/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 784
Language: TypeScript

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Deploying to Staging Environment ## Overview The staging environment deployment is a coordinated multi-repo process that synchronizes code across three repositories (relay, relay-dashboard, relay-cloud) and automatically triggers deployment via GitHub Actions. Staging deployments ensure feature verification before production while keeping main branch clean during development. ## When to Use - **Integrating features across repos** - Multiple components depend on changes in different repos - **Testing feature branches together** - Verify feature branch changes don't break integration - **Promoting main to staging** - Standard sync to keep staging up-to-date with latest main - **Verifying deployment readiness** - Test infrastructure changes or deployment workflows - **Cross-team coordination** - Share feature branches for integration testing **When NOT to use:** - Emergency hotfixes (use production deployment instead) - Single-repo changes only (push directly if not blocking other repos) - Testing without intent to deploy (use local environment instead) ## Architecture The staging deployment system consists of: ``` Three Repos (relay, relay-dashboard, relay-cloud) ↓ Staging Branches

What's inside
Steps it walks through
  1. Overview
  2. When to Use
  3. Architecture
  4. Quick Reference
  5. Standard Workflow (All Repos)
  6. Relay-Dashboard
  7. Relay-Cloud (Triggers Deployment)
  8. Implementation
  9. Why Git Worktrees?
  10. Step-by-Step Deployment Process
  11. Pushing Feature Branches to Staging
  12. Common Mistakes
  13. Workflow Details
  14. deploy-staging.yml Behavior
Commands it runs
cd /data/repos/relay
git worktree add .worktrees/staging-push main
cd .worktrees/staging-push
git fetch origin main:main
git push origin main:staging
git fetch origin feature/your-branch:feature/your-branch
git push origin feature/your-branch:staging
git worktree remove .worktrees/staging-push
cd /data/repos/relay-dashboard
cd /data/repos/relay-cloud
More from relay
All skills →
About this skill
What does the deploying-to-staging-environment skill do?

Use when deploying changes to staging across relay, relay-dashboard, and relay-cloud repos - coordinates multi-repo branch syncing using git worktrees, automatically triggers staging deployments via GitHub Actions

How do I install it?

Run `npx skills add AgentWorkforce/relay --skill deploying-to-staging-environment --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From AgentWorkforce/relay, a repository with 784 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going