Git
Git Commit Message Linter
Checks your commit subject line against the Conventional Commits spec (type(scope): description), with exact pass/fail reasons for each rule.
Valid Conventional Commits format
Format checks (hard fail if broken)
Scope "(api)" is well-formed.
Type "feat" is a valid Conventional Commits type.
Exactly one space after the colon.
Description is present.
Style tips (informational, non-blocking)
Description starts lowercase.
No trailing period.
Subject line is 43 characters - within the ~72 char guideline.
Valid types
featfixdocsstylerefactorperftestbuildcichorerevertChecks the Conventional Commits format of the subject (first) line only.
This is one question. ArchSetu answers it for a whole repository.
Call graph, dead code, blast radius and a health score, in about a minute.
Related tools
All Git tools →CODEOWNERS GeneratorPath patterns to owners - valid CODEOWNERS file, bottom-to-top matching explained..gitattributes GeneratorLine endings, language diff settings, Git LFS, and vendored paths in one file.Git Hooks GeneratorPick a hook type and checks, get a working shell script plus install steps.Branch Naming Convention CheckerCheck a branch name against type/description, Jira-style, or kebab-case.Squash vs Merge vs Rebase ExplainerWhat you care about to a recommended merge strategy, with the real tradeoffs shown.Merge Conflict Complexity EstimatorFile overlap and edit density between two branches to a conflict-risk score before you merge.
Was this tool helpful?