Release Marshal

Overview

Orchestrate the full delivery flow for the current project. Calling this skill is the normal commit → Jira → PR workflow; do not introduce a separate "commit-task-PR" mode.

1. Prepare clean gitflow commits.
2. Rebase safely onto develop or the selected base branch.
3. Create or reuse Jira Server/Data Center issue and subtask.
4. Create a GitHub pull request with a factual body and Jira link.
5. Offer to move the associated Jira task to review after the PR is created.

The marshal directs specialized skills instead of duplicating their detailed workflows:

• krt:gitflow-knight owns branch hygiene, staging, and commit planning.
• krt:rebase-smith owns clean branch history and safe rebase decisions.
• krt:jira-scribe owns Jira issue/subtask lookup, creation proposals, sprint handling, and transitions.
• gh owns GitHub remote state, push/PR operations, and reviewer requests after confirmation.