wa:deploy-tracker

You can automatically update tracker issue states after deployment by resolving target issue keys and applying status transitions based on commit and PR context. This skill transitions GitHub, JIRA, or Linear issues to deployed stages with completion metadata like commit SHA and ISO-8601 timestamps.

Yes, you can infer issue keys for deployment tracking from the current branch name, or extract them from arguments and TASKS.md. The system multi-targets issues and applies status transitions with completion metadata like commit SHA and PR URL.

Deployment tracking works without a configured tracker backend by falling back to local markdown workflows. When GitHub, JIRA, or Linear backends are unavailable, it updates TASKS.md directly and appends completion notes with commit SHA and timestamps.

When updating deployment status, the system attaches completion metadata including the commit SHA, PR URL when available, and an ISO-8601 UTC timestamp. This metadata is applied to each issue during the CI/CD status transition process.

When tracker configuration is missing, the system falls back to local markdown updates in TASKS.md. It also includes robust handling for per-issue update failures, ensuring that individual transition errors do not halt the entire deployment tracking batch.

Yes, MCP preflight validation is required to transition issue states for configured tracker types. This validation ensures the tracker backend is properly resolved via tracker:router before attempting any deployment status transitions.