krt:release-marshal
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.
- Prepare clean gitflow commits.
- Rebase safely onto
developor the selected base branch. - Create or reuse Jira Server/Data Center issue and subtask.
- Create a GitHub pull request with a factual body and Jira link.
- 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-knightowns branch hygiene, staging, and commit planning.krt:rebase-smithowns clean branch history and safe rebase decisions.krt:jira-scribeowns Jira issue/subtask lookup, creation proposals, sprint handling, and transitions.ghowns GitHub remote state, push/PR operations, and reviewer requests after confirmation.
More from elzawarudo/krt
krt-compound-master
>
11krt-release-marshal
Orchestrate the full delivery flow for the current project repository: direct krt-gitflow-knight for clean commits, krt-rebase-smith for clean branch history, krt-jira-scribe for Jira Server/Data Center issue work, then open a GitHub pull request with a factual body and Jira link. Use when the user asks to create/open a PR, prepare a pull request, ship current work, publish branch changes for review, or run the full gitflow + rebase + Jira + PR workflow. Runtime aliases may expose this as krt:release-marshal.
10krt-gitflow-knight
>
10krt-rebase-smith
>
8krt-jira-scribe
Manages Jira Server/Data Center issues on a Spanish-language instance. Verifies existing global issues and subtasks, checks whether new work belongs under an existing parent, proposes Spanish issue/subtask creation when missing, handles active sprint placement, and manages Spanish transitions. Runtime aliases may expose this as krt:jira-scribe.
8krt-ci-questor
Investigate CI/CD failures and produce concise cause reports. Use when a user asks why a GitHub Actions, GitLab CI, CircleCI, Jenkins, or other pipeline failed; needs log triage, flaky-test assessment, runner/dependency/config diagnosis, failed-check summaries, rerun guidance, or a simple report explaining what happened and what to do next. Runtime aliases may expose this as krt:ci-questor.
7