Description
My projects often setup pre-commit (with https://pre-commit.com/ or https://prek.j178.dev/) to do linting, format checking at git commit.
When the linting + format checking does not pass, there is no files to be committed, they are still in stage or unstage.
But after resolving, Crush does git commit --amend and cause mess with Git history. Even though that it can fix by many steps of reset, stash, re-commit, it is better that it does not do git commit --amend from beginning.
I think the system prompt should tell Crush to check the pre-commit output to check if any files are committed or not.
Version
v0.87.0
Environment
Ubuntu 26.04, Ghostty
Description
My projects often setup pre-commit (with https://pre-commit.com/ or https://prek.j178.dev/) to do linting, format checking at
git commit.When the linting + format checking does not pass, there is no files to be committed, they are still in stage or unstage.
But after resolving, Crush does
git commit --amendand cause mess with Git history. Even though that it can fix by many steps of reset, stash, re-commit, it is better that it does not dogit commit --amendfrom beginning.I think the system prompt should tell Crush to check the pre-commit output to check if any files are committed or not.
Version
v0.87.0
Environment
Ubuntu 26.04, Ghostty