Git & Dev Utility Tools
The unglamorous half of working in a repository: a .gitignore that ignores what you meant, a commit message that survives review and release automation, a licence file with the right text, and a diff you can actually read. Every tool runs locally — no repository is cloned, no registry is contacted and nothing you paste leaves the page.
Most popular
- gitgitignore Generator● ready
Pick the stacks you use and get one commented .gitignore file — duplicates removed, entries in a sensible order, plus a syntax check on your own patterns.
- gitCommit Linter● ready
Header structure, allowed types, scope format, imperative mood, header length, the blank line before the body and BREAKING CHANGE footers — with a score.
- gitDiff Viewer● ready
Understands added, deleted, renamed, copied, binary and mode-only changes, tracks hunk line numbers, and reports lines it could not place instead of hiding them.
- gitLicense● ready
Short permissive licences in full (MIT, ISC, BSD, 0BSD, Unlicense), the official header plus canonical link for the long ones, and a comparison of what each permits.
- gitSemver Bumper● ready
Handles the cases people get wrong: releasing a prerelease, incrementing a prerelease counter, switching identifiers from alpha to beta, and premajor versions.
Repository Files
- gitgitignore Generator● ready
Pick the stacks you use and get one commented .gitignore file — duplicates removed, entries in a sensible order, plus a syntax check on your own patterns.
- gitgitignore Checker● ready
Paste your rules and a path to get a yes/no verdict, the matching rule, the equivalent git check-ignore command, and the reasons a negation never fires.
- gitdockerignore Generator● ready
Node modules, build output, .git, secrets, docs and tests as one-click blocks, merged with your own patterns and checked for the syntax Docker handles differently.
- giteditorconfig● ready
Indent style and size, line endings, charset, trailing whitespace and final newline, plus blocks that keep tabs in Makefiles and trailing spaces in Markdown.
- gitCODEOWNERS● ready
Rules in match order, owners validated as @user, @org/team or email, a fallback rule that catches everything, and warnings for the ordering mistake that silently disables rules.
- git.gitconfig● ready
The settings worth changing from the defaults, plus a curated alias set — with checks for the combinations that break git outright, like signing without a key.
- gitLicense● ready
Short permissive licences in full (MIT, ISC, BSD, 0BSD, Unlicense), the official header plus canonical link for the long ones, and a comparison of what each permits.
Commits & Releases
- gitCommit Linter● ready
Header structure, allowed types, scope format, imperative mood, header length, the blank line before the body and BREAKING CHANGE footers — with a score.
- gitCommit Generator● ready
Answer a few fields and get a correctly formatted message with the `!` marker, BREAKING CHANGE footer and Closes/Refs lines placed where tooling expects them.
- gitSemver Bumper● ready
Handles the cases people get wrong: releasing a prerelease, incrementing a prerelease counter, switching identifiers from alpha to beta, and premajor versions.
- gitSemver Compare● ready
See which version is greater, why, and how big the jump is — including the prerelease ordering that most hand-written comparisons get wrong.
- gitTag Validator● ready
Reports the characters and sequences git refuses, warns when a numeric tag is not strict semver, and checks the new tag moves forward from the previous one.
- gitCHANGELOG● ready
Groups commits into Added, Fixed, Changed, Breaking and the rest, links each hash when you give it a repository URL, and lists the lines it could not classify.
- gitBranch Names● ready
Slugifies accents and punctuation, keeps the prefix intact when shortening, and checks the result against Git's own ref-naming rules.
Diffs & History
- gitDiff Viewer● ready
Understands added, deleted, renamed, copied, binary and mode-only changes, tracks hunk line numbers, and reports lines it could not place instead of hiding them.
- gitConflict Cleaner● ready
See every conflicted block side by side, decide on each one, and copy out a file with no markers left — including diff3 blocks with a common-ancestor section.
- gitCommit Hash● ready
Detects non-hex characters, wrong lengths and uppercase output, reports the SHA-1 or SHA-256 algorithm, and computes the shortest unique abbreviation git would print.
- gitGitHub URL● ready
Repository, file, branch, pull request, issue, commit, compare, release, gist and raw URLs — with the clone, SSH and API URLs ready to copy.
- gitGit Commands● ready
Fifty-plus commands across inspecting, staging, branching, undo, history rewriting, remotes, merges, stashes and debugging — with syntax and a real example.
Project Health
- gitpackage.json Check● ready
Catches what npm only tells you at publish time — invalid names, non-semver versions, broken dependency specs, cross-section duplicates and duplicate JSON keys.
- gitpackage.json Diff● ready
Per-section tables for dependencies, devDependencies, peer and optional dependencies, scripts and engines, plus the version bump between the two files.
- gitGit Hooks● ready
Shell hooks for your package manager's own scripts, or the Python pre-commit framework config, with commit-message patterns and Husky setup for teams.
- gitPR Description● ready
Summary, type of change, what changed, how to test, breaking changes, screenshots and a pre-ticked checklist — with `Closes #123` links.
- gitREADME Checklist● ready
Installation, usage, API, configuration, contributing, tests, licence and more — detected from the text, with quality notes for alt text, unlabelled code blocks and placeholders.
All tools
- gitgitignore Generator● ready
Pick the stacks you use and get one commented .gitignore file — duplicates removed, entries in a sensible order, plus a syntax check on your own patterns.
- gitdockerignore Generator● ready
Node modules, build output, .git, secrets, docs and tests as one-click blocks, merged with your own patterns and checked for the syntax Docker handles differently.
- gitgitignore Checker● ready
Paste your rules and a path to get a yes/no verdict, the matching rule, the equivalent git check-ignore command, and the reasons a negation never fires.
- gitCommit Linter● ready
Header structure, allowed types, scope format, imperative mood, header length, the blank line before the body and BREAKING CHANGE footers — with a score.
- gitCommit Generator● ready
Answer a few fields and get a correctly formatted message with the `!` marker, BREAKING CHANGE footer and Closes/Refs lines placed where tooling expects them.
- gitSemver Bumper● ready
Handles the cases people get wrong: releasing a prerelease, incrementing a prerelease counter, switching identifiers from alpha to beta, and premajor versions.
- gitSemver Compare● ready
See which version is greater, why, and how big the jump is — including the prerelease ordering that most hand-written comparisons get wrong.
- gitBranch Names● ready
Slugifies accents and punctuation, keeps the prefix intact when shortening, and checks the result against Git's own ref-naming rules.
- gitCommit Hash● ready
Detects non-hex characters, wrong lengths and uppercase output, reports the SHA-1 or SHA-256 algorithm, and computes the shortest unique abbreviation git would print.
- giteditorconfig● ready
Indent style and size, line endings, charset, trailing whitespace and final newline, plus blocks that keep tabs in Makefiles and trailing spaces in Markdown.
- gitCODEOWNERS● ready
Rules in match order, owners validated as @user, @org/team or email, a fallback rule that catches everything, and warnings for the ordering mistake that silently disables rules.
- git.gitconfig● ready
The settings worth changing from the defaults, plus a curated alias set — with checks for the combinations that break git outright, like signing without a key.
- gitLicense● ready
Short permissive licences in full (MIT, ISC, BSD, 0BSD, Unlicense), the official header plus canonical link for the long ones, and a comparison of what each permits.
- gitpackage.json Check● ready
Catches what npm only tells you at publish time — invalid names, non-semver versions, broken dependency specs, cross-section duplicates and duplicate JSON keys.
- gitpackage.json Diff● ready
Per-section tables for dependencies, devDependencies, peer and optional dependencies, scripts and engines, plus the version bump between the two files.
- gitGit Hooks● ready
Shell hooks for your package manager's own scripts, or the Python pre-commit framework config, with commit-message patterns and Husky setup for teams.
- gitREADME Checklist● ready
Installation, usage, API, configuration, contributing, tests, licence and more — detected from the text, with quality notes for alt text, unlabelled code blocks and placeholders.
- gitCHANGELOG● ready
Groups commits into Added, Fixed, Changed, Breaking and the rest, links each hash when you give it a repository URL, and lists the lines it could not classify.
- gitConflict Cleaner● ready
See every conflicted block side by side, decide on each one, and copy out a file with no markers left — including diff3 blocks with a common-ancestor section.
- gitDiff Viewer● ready
Understands added, deleted, renamed, copied, binary and mode-only changes, tracks hunk line numbers, and reports lines it could not place instead of hiding them.
- gitGitHub URL● ready
Repository, file, branch, pull request, issue, commit, compare, release, gist and raw URLs — with the clone, SSH and API URLs ready to copy.
- gitTag Validator● ready
Reports the characters and sequences git refuses, warns when a numeric tag is not strict semver, and checks the new tag moves forward from the previous one.
- gitPR Description● ready
Summary, type of change, what changed, how to test, breaking changes, screenshots and a pre-ticked checklist — with `Closes #123` links.
- gitGit Commands● ready
Fifty-plus commands across inspecting, staging, branching, undo, history rewriting, remotes, merges, stashes and debugging — with syntax and a real example.
About Git & Dev Utility Tools
Git is a small vocabulary with a large surface area: a .gitignore rule that looks correct behaves differently depending on where the slash is, an abbreviation that is unique in one repository may be ambiguous in another, and a `--hard` reset where you wanted `--mixed` deletes an afternoon. This category handles those details locally. The ignore-file tools implement git's own matching algorithm — last match wins, an ignored directory hides its whole subtree — so the verdict matches git check-ignore. The commit tools parse Conventional Commits for real, so a message that lints clean also groups correctly in a generated changelog. The diff viewer is a parser, not a highlighter: it tracks hunk line numbers, rename and copy headers, mode-only changes and binary stubs. And the repository-file generators (editorconfig, dockerignore, CODEOWNERS, .gitconfig, LICENSE) produce files you can copy straight into a project, with the caveats stated rather than buried — including which licences this tool writes in full and which it points at the canonical source instead.
Related categories
- Code Formatter Tools
Format, minify and inspect HTML, CSS, SQL, JavaScript and more — right in your browser.
- YAML Tools
Validate, format, and convert YAML config files in your browser.
- JSON Tools
Validate, format, and convert JSON instantly in your browser.
- Text Tools
Format, transform, and analyze text quickly.
Frequently asked questions
Which gitignore rules do these tools actually implement?
Git's own matcher: `*` and `?` never cross a slash but `**` does, a pattern containing a slash is anchored to the ignore file's directory, a trailing slash means directories only, `!` re-includes, and the last matching rule wins. The one rule that trips everyone up is also implemented — a file inside an ignored directory cannot be re-included — so the verdict matches what git check-ignore prints.
Do these tools need access to my repository?
No. Everything works on text you paste: the ignore matcher reads the rules and a path, the diff viewer reads a patch, the package.json tools read two files. Nothing is cloned, no GitHub API is called, and the tools keep working with the network switched off.
Is the licence text safe to ship?
For MIT, ISC, BSD-2-Clause, BSD-3-Clause, 0BSD and Unlicense the full text is written out. For Apache 2.0, GPL, LGPL, AGPL, MPL, EPL and CC0 — which run to thousands of words of numbered clauses — the tool writes the official file header, the SPDX identifier and the canonical URL to copy from, because reproducing that text from memory would risk a subtle and potentially load-bearing error.
Can I use these in CI instead of locally?
The logic is plain TypeScript with no DOM access, so the same functions could be imported into a pipeline script. As pages they are browser-only by design; for enforcement in CI use the equivalent established tools — commitlint for messages, prettier for formatting, gitleaks for secrets — whose configuration the generators here are designed to match.
What is the difference between .gitignore and .dockerignore?
They exclude files from different things: .gitignore keeps files out of the repository, .dockerignore keeps them out of the Docker build context. The syntax is close enough that the same pattern usually means the same thing, but Docker evaluates patterns from the context root and handles a trailing slash slightly differently, which is why the two generators keep their presets separate.