Nekonote Toolbox logo

Nekonote Toolbox

Free browser-based tools for developers and IT admins.

日本語

Git Commit Message Generator

Build a commit message in the Conventional Commits format (type(scope): subject) from separate fields, with a live preview and checks for the usual style problems.

0 characters in the subject (0 in the whole first line; aim for 50, hard limit 72)

Preview 

                            

                            

                                
                                
                                
                                

                            

                        

                    

                


                

                    
About this tool

                    
Conventional Commits gives every commit message the same shape — a type, an optional scope, a short subject, an optional body and optional footers — so that changelogs and version bumps can be generated from the history and reviewers can scan it quickly. This tool assembles that message from separate fields and checks it as you type.

                    
Everything runs in your browser. What you type is never sent to a server.

                


                

                    
How it works

                    
    
                        
  • First line: type, then the scope in parentheses if you gave one, then ! for a breaking change, then a colon, a space and the subject. Example: feat(auth)!: drop support for legacy tokens.
    • 
                        
  • Body is placed after one blank line. Footers come after another blank line. For a breaking change the generator adds a BREAKING CHANGE: … footer line first, followed by your own footer text.
    • 
                        
  • Checks: a missing subject; a first line longer than 50 characters (advice) or 72 characters (error); a subject that ends with a period, starts with a capital letter, or begins with a past-tense verb such as “added” or “fixed” instead of the imperative; a scope containing spaces or parentheses; body lines longer than 72 characters; footer lines that do not look like Token: value or Token #value; and a breaking change without details.
    • 
                        
  • Length is counted in characters as JavaScript sees them (UTF-16 units), so an emoji counts as 2. Git itself does not enforce any of these limits; they are conventions.
    • 
                        
  • The checks are advice, not rules: the message is always generated, and you can copy it even when there are warnings.
    • 
                        
  • The tool does not run git or read your repository. Paste the copied message into git commit or your Git client.
    • 
                    

                    
FAQ

                    

                        
Q. How do I use the copied message on the command line?

                        
A. Run git commit and paste it into the editor, or save it to a file and run git commit -F that-file. Pasting into a quoted -m string works for a one-line message but is awkward for multi-line ones.

                    

                    

                        
Q. Do I need a scope?

                        
A. No. A scope is a short noun for the area you touched, such as auth or parser. Leave it empty if it would not help the reader.

                    

                    

                        
Q. What is the difference between ! and BREAKING CHANGE?

                        
A. Both mark an incompatible change. The ! after the type or scope is the short form; the BREAKING CHANGE footer carries the explanation. This tool adds both when you tick the box.