Rewritten
Require active user in access check
Previously any existing user passed the check; now the user must also be active, preventing deactivated accounts from retaining access.
About this tool
By the time you're staging changes, you've already spent your focus on the code — and the commit message becomes an afterthought like "fix stuff." This tool reads a diff and writes a proper commit message: a concise imperative subject line and, when the change warrants it, a short body explaining the why. It's built for developers who want a readable git history without composing each message by hand, and it follows the conventions reviewers expect.
Frequently asked questions
Does it follow Conventional Commits format?+
It writes a clean imperative subject and optional body by default. If you use the `type(scope): subject` convention, mention it and it will follow that format.
How big a diff can I paste?+
Small, focused diffs produce the best messages. For a large diff spanning many concerns, consider splitting it into separate commits first.
Will it explain why, not just what?+
It infers intent from the change and includes a body when the reasoning isn't obvious from the subject alone.