Gitflow Knight

Overview

Create clean, user-approved commits following a gitflow-style process: correct branch first, then plan commits, then execute them.

Workflow

0) Operating rules (non-negotiable)

• Never add "Co-authored-by" lines (or any LLM attribution) to commit messages.
• Use one commit-plan acceptance gate when acting standalone. If this skill is running inside an already accepted krt-release-marshal workflow, do not add extra approval gates for local/reversible steps unless required information is missing or the action becomes destructive/external.
• Prefer non-interactive commands. Avoid git add -p unless the user explicitly wants an interactive hunk workflow.
• Use the host runtime's command wrapper only when the current repo requires one. The command examples below use plain git for portability.
• Do not run tests, linters, or formatters unless the user explicitly asks.

1) Preflight (do not change anything yet)