From tac
Validates ZTE workflow state (fields, worktree, branch), merges feature branch to main with no-ff, pushes to origin for production deployment.
How this skill is triggered — by the user, by Claude, or both
Slash command
/tac:shipThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Validate workflow state and merge to main for production deployment.
Validate workflow state and merge to main for production deployment.
$1: Branch name to mergeYou are the ship command - the final step in Zero-Touch Engineering. Validate everything is ready, then merge to main.
Before shipping, ALL these fields must be populated:
adw_id - Workflow identifierissue_number - GitHub issue being resolvedbranch_name - Branch with changesplan_file - Implementation plan pathissue_class - Task classificationworktree_path - Isolated environment path (if using worktrees)If any field is missing or empty, ABORT and report what's missing.
If using worktrees, perform three-way validation:
worktree_path fieldgit worktree list)If validation fails, ABORT and report the issue.
git branch --list $1
If branch doesn't exist, ABORT.
git fetch origin
git checkout main
git pull origin main
Merge with no-fast-forward to preserve commit history:
git merge $1 --no-ff -m "Merge branch '$1' into main"
If merge conflicts occur, ABORT and report conflicts.
git push origin main
Report successful ship:
Shipped: Branch $1 merged to main and pushed to origin
Return structured result:
{
"success": true,
"branch": "$1",
"merged_to": "main",
"commit": "{merge_commit_hash}",
"pushed": true
}
Or on failure:
{
"success": false,
"reason": "{failure_reason}",
"step_failed": "{step_name}",
"remediation": "{suggested_fix}"
}
This command has multiple abort points:
--no-ff to preserve full commit historynpx claudepluginhub melodic-software/claude-code-plugins --plugin tacRuns verification checks, reviews the diff, picks the integration path (merge, PR, squash, stacked PR), writes the PR/merge message, pushes, and cleans up branches and worktrees.
Use when implementation is finished, tests are green, and you need to decide how to land the work - presents structured integration paths for local merge, pull request, deferral, or abandonment
Guides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.