Looks interesting, but there are aspects about how it's presented and needs to be downloaded that is a bit questionable.
1) If this is not meant for just a Japanese audience, then at least have an obvious English translation.
Google translate is doing an OK job, so at least put that up (just indicate machine translation).
2) Directing people to download from Google Drive or Hugging Face seems less than ideal.
SourceForge (https://sourceforge.net/) might be another acceptable option. Both because it can be used to mirror what is at GitHub and can be used to host larger files (though still a depends type of thing). At the very least, they are more well known and trusted.
You are right, though kind of easy to miss, relative to everything on that page. Maybe it should say English translation or English Readme in larger letters for the non-attentive people :-)
IMO, in small/solo development projects, you really don't need particularly descriptive git messages.
I'll frequently commit 40 disparate changes under "stuff" in my personal projects. It's never been a problem. No real need to LARP a big software project with many developers.
If your productivity completely falls apart without good commit messages (or any particular tool, say git), that is symptomatic of poorly structured work and poor planning.
To be fair, function names also tells you what the code is intended to do.
Git based workflows were not the missing technology that finally unlocked the development of complex systems. We wrote complex code before we had git annotate, even before version control systems were widely adopted.
It was considered good practise to write meaningful commit comments from the very first version control systems, long before git was invented.
Source: I have had commits rejected on code review for insufficiently descriptive commit messages in RCS, SCCS, Visual SourceSafe and CVS and probably others before git was first invented.
In your solo projects (which is the context for this discussion), who is doing these code reviews?
What is a sane practice varies immensely with the scale and scope of the project. Many things that are nearly mandatory for large scale development are pointless obstacles in small scale development.
1) If this is not meant for just a Japanese audience, then at least have an obvious English translation.
Google translate is doing an OK job, so at least put that up (just indicate machine translation).
2) Directing people to download from Google Drive or Hugging Face seems less than ideal.
SourceForge (https://sourceforge.net/) might be another acceptable option. Both because it can be used to mirror what is at GitHub and can be used to host larger files (though still a depends type of thing). At the very least, they are more well known and trusted.