Summary
git-qcommit generates commit messages via the Amazon Q CLI chat. We've largely moved to Kiro as our coding agent, so we want a sibling command, git-kcommit, that does the same thing using Kiro instead of q.
Motivation
- Day-to-day AI work now goes through kiro, not
q.
- Keep the familiar
git-?commit UX; only the AI backend differs.
Proposed scope
- Add a
git-kcommit entrypoint mirroring git-qcommit, swapping the q chat invocation for the Kiro equivalent.
- Extract the shared staging / diff-gathering / commit logic into a common core so
git-qcommit and git-kcommit are thin backend-specific frontends.
- Decide between a selectable
--backend q|kiro flag on one tool vs. shipping a second binary.
Filed via the autoloop ↔ GitHub gh-sync bridge (createIssue path) as a live contract test of the issue-sync feature.
Summary
git-qcommitgenerates commit messages via the Amazon Q CLI chat. We've largely moved to Kiro as our coding agent, so we want a sibling command,git-kcommit, that does the same thing using Kiro instead ofq.Motivation
q.git-?commitUX; only the AI backend differs.Proposed scope
git-kcommitentrypoint mirroringgit-qcommit, swapping theq chatinvocation for the Kiro equivalent.git-qcommitandgit-kcommitare thin backend-specific frontends.--backend q|kiroflag on one tool vs. shipping a second binary.Filed via the autoloop ↔ GitHub
gh-syncbridge (createIssue path) as a live contract test of the issue-sync feature.