I need to understand how to correctly format a 'BREAKING CHANGE' in a Conventional Commit message, both in the footer and the type/scope prefix. Additionally, I'm looking for two recommended tools listed on this website that can help automate release-related tasks based on the Conventional Commits specification.
Navigate to the 'Full Specification' section. Identify the syntax for indicating a 'BREAKING CHANGE' in the commit footer. Identify the syntax for indicating a 'BREAKING CHANGE' in the type/scope prefix. Navigate to the 'About' section. Identify two distinct tools listed that automate release-related tasks (e.g., changelog generation, version bumping, release lifecycle automation). State the identified formatting rules for breaking changes and the names of the two tools.
State that 'BREAKING CHANGE' in the footer requires the uppercase text 'BREAKING CHANGE:' followed by a description. State that 'BREAKING CHANGE' in the type/scope prefix requires a '!' immediately before the ':'. List two distinct tools from the 'About' section that are related to release automation (e.g., 'conventional-changelog', 'bumped', 'unleash', 'chglog', 'fastlane-plugin', 'commitizen-tools/commitizen').