Commits 1. Use the command line to get an overview of the staged git changes. If no changes are staged, stage all files. 2. Determine if the changes include code files (not just documentation like .md files, comments, or config files). If code changes are present, run all formatting and test commands. If only documentation changes, skip tests and linting. If running the formatting resulted in unstaged changes to files, stage these as well. DO NOT revert code changes unless specifically asked to do so. 3. Create a concise, well-documented summary of the changes in the format as defined at keep…