.gitmessage

#<type>[optional scope]: <description>

#[optional body]

#[optional footer(s)]

###
## Type
# build: Changes that affect the build system or external dependencies (example scopes: cargo, broccoli, npm)
# ci: Changes to our CI configuration files and scripts (example scopes: github, pre-commit)
# docs: Documentation only changes
# feat: A new feature
# fix: A bug fix
# perf: A code change that improves performance
# refactor: A code change that neither fixes a bug nor adds a feature
# style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
# test: Adding missing tests or correcting existing tests
#
## Scope
# The scope should be the name of the npm package affected (as perceived by the person reading the changelog generated from commit messages.
#
# The following is the list of supported scopes (subject to change):
# core
# character
# blood
# stats
# attributes
# JSON
# list
# create
# print