deploy

Route backend deployments to hardened scripts with branch and repository safety gates.

Updated Jul 5, 2026
One-click install
npx skills add https://github.com/danwan/coding-agent --skill deploy-danwan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deploy
Source: https://github.com/danwan/coding-agent/tree/main/sources/skills/deploy
Command: npx skills add https://github.com/danwan/coding-agent --skill deploy-danwan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents unsafe, manual deployment anti-patterns by enforcing a strict, gated workflow that ensures the working tree is clean, synced, and verified before any production or development deployment occurs.

Core Features & Use Cases

  • Hardened Routing: Automatically routes deployment requests to project-specific, hardened shell scripts while preventing manual CLI fallbacks.
  • Safety Gates: Enforces critical checks including branch-to-environment mapping, clean-tree verification, and origin synchronization.
  • Use Case: When you need to push a backend update to production, this skill ensures your local branch is synced with origin and that the deployment script is executed without exposing sensitive environment variables or bypassing project-defined safety protocols.

Quick Start

Use the deploy skill to safely push the current branch to the appropriate backend environment.

Frequently Asked Questions about deploy

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

FAQPage Schema
How do I prevent manual CLI overrides during backend deployment?

To prevent manual CLI overrides during backend deployment, use a gated workflow that routes execution to hardened project scripts. This enforces strict safety protocols by prohibiting shell-expanded key usage and manual fallbacks, ensuring secure deployments.

What are the safety requirements for deploying to production with Modal or Convex?

Production deployment safety requirements for Modal or Convex include strict branch-to-environment mapping, clean working tree verification, and complete origin synchronization. These safety gates prevent unsafe updates from reaching production environments.

How do I automate backend deployments without exposing sensitive environment variables?

Automate backend deployments without exposing sensitive environment variables by routing requests through hardened shell scripts. This gated approach executes deployment workflows while enforcing security protocols that prohibit shell-expanded key usage.

Can I deploy to development environments with uncommitted local changes?

No, you cannot deploy to development environments with uncommitted local changes. The deployment workflow enforces clean-tree verification and origin synchronization, requiring your local branch to be completely clean and synced before any deployment occurs.

What happens if my local branch is not synced with origin before deployment?

If your local branch is not synced with origin before deployment, the deployment process fails its safety gate checks. The workflow validates branch status and origin synchronization, blocking execution until your local repository is completely synced with the remote.

What is the best way to enforce environment-specific deployment rules for backend updates?

The best way to enforce environment-specific deployment rules is by using a gated workflow that validates branch-to-environment mapping and repository cleanliness. This hardened routing ensures only verified branches reach their designated environments, preventing unsafe anti-patterns.