skills.rest
nghiahsgs
nghiahsgsCOMMUNITY
Explore all skills by this author →
GitHub

taw-deploy

Forward deployment commands to the main /taw workflow.

32|13|Updated Apr 21, 2026
Search Tags:#workflow#compatibility#cli#deploy#shim#taw
One-click install
npx skills add https://github.com/nghiahsgs/taw-kit --skill taw-deploy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: taw-deploy
Source: https://github.com/nghiahsgs/taw-kit/tree/main/skills/taw-deploy
Command: npx skills add https://github.com/nghiahsgs/taw-kit --skill taw-deploy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This backward-compatible shim forwards deployment-related commands to the main /taw workflow, ensuring legacy taw-kit users can trigger deployments without changing their workflows.

Core Features & Use Cases

  • Forwards /taw deploy calls to the standard deployment path.
  • Preserves compatibility for older taw-kit versions while the main workflow evolves.
  • Serves as a temporary bridge until users migrate fully to the latest /taw usage.

Quick Start

Run /taw deploy (or /taw đẩy lên vercel) to trigger deployment through the main taw workflow.

Frequently Asked Questions about taw-deploy

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

FAQPage Schema
How do I maintain backward compatibility when deploying with an older taw-kit setup?▼

To maintain backward compatibility, use the taw-deploy shim which forwards deployment commands directly to the standard /taw workflow, allowing legacy taw-kit setups to trigger deployments without changing existing workflows.

What is a deploy shim and when do I need it for my workflow?▼

A deploy shim is a wrapper that intercepts commands and forwards them to a main workflow. You need it when legacy scripts invoke outdated deployment paths, ensuring they route to the current standard deployment without modification.

How do I trigger a deployment through the standard taw workflow?▼

You trigger a deployment by running the /taw deploy command. The command is automatically routed through the standard deployment path via the ship branch, requiring no new dependencies or workflow modifications.

Do I need to install new dependencies to use the taw-deploy compatibility wrapper?▼

No, you do not need to install new dependencies. The taw-deploy compatibility wrapper relies solely on the existing /taw deployment path and acts purely as a forwarding mechanism to the main workflow.

When should I stop using the taw-deploy shim for my deployments?▼

You should stop using the taw-deploy shim once you fully migrate your legacy taw-kit usage to the latest /taw workflow commands, as it only serves as a temporary bridge for backward compatibility.

Related Skills

Explore More Software Engineering Skills→
nghiahsgsnghiahsgs
32

taw-add

Forward legacy taw-add invocations to the /taw command.

Community
Basic
nghiahsgsnghiahsgs
32

taw-security

Forwards legacy taw-security audit requests to the /taw workflow.

Community
Basic
DYAI2025DYAI2025
3

finishing-a-development-branch

Verify tests and execute merge, PR, keep, or cleanup workflows for a development branch.

Community
Intermediate
nghiahsgsnghiahsgs
32

taw-new

Forward preset-based taw-new requests to the main /taw workflow.

Community
Basic