Commits
gstack’s /careful stops asking about words in your commit messages
The /careful hook in gstack checked your whole command, so a commit message that said prevent drop table asked for approval as a database drop. Now the words inside a commit message pass straight through.
Heredocs
The heredoc message agents write most is covered
That includes the form agents write most often: a multi-line message passed in through a heredoc. Amended commits, commits run against another folder, and every message flag are covered too.
Still asks
Everything around the message is still checked
The guard still asks about everything around the message: a command on the next line, another command's message flag, and a pipe after the commit. The rules that block outright still read the whole command.
Limits
Two commit forms can still ask about message words
Two forms are still not covered: a message fed to git on standard input, and a commit that follows sudo or an environment variable. A risky word there still stops you.
Verdict
If you run /careful, I would upgrade now
CHANGELOG.mdgarrytan/gstack · 1.91.212.0If you run /careful with Claude Code, I would upgrade now: commits stop pausing over their own wording, and every real command still gets checked. The full notes are in the gstack changelog.
