Check a proposed Git branch name before it reaches a remote. The validator applies Git ref restrictions, catches confusing path patterns, and optionally enforces a team-friendly lowercase convention. It reports every failed rule instead of stopping at the first problem, so names copied from tickets or release notes are easier to clean up.
Check a proposed Git branch name before it reaches a remote. The validator applies Git ref restrictions, catches confusing path patterns, and optionally enforces a team-friendly lowercase convention. It reports every failed rule instead of stopping at the first problem, so names copied from tickets or release notes are easier to clean up.
This is a client-side preflight check. A server can still reject a valid name because of repository-specific rules.
The bundled sample demonstrates the expected input. Select Sample, run the analyzer, and compare the detailed output with the summary metrics.
feature/add-search
Checks Git ref safety first, then applies optional lowercase kebab-style and allowed-prefix policies.
This is a client-side preflight check. A server can still reject a valid name because of repository-specific rules.
Paste plain text directly into the input box. The parser runs locally in the browser and does not send it to a server.
Moderate source and configuration files work well. Browser memory and algorithm limits may apply to unusually large input.
No. It only analyzes or transforms the text you provide and makes no repository or database connection.
Repository policies, SQL dialects, and parser behavior vary. Treat the result as a focused preflight check and confirm project-specific rules.
Yes. Run the tool, then use Download for the primary result or the JSON and CSV buttons when structured data is available.
| Field | Meaning |
|---|---|
| Output | Copy-ready primary result |
| Summary | Counts and completion status |
| Interpretation | Limits and next review step |
Browse more checks, parsers, and generators in this category.
Open category hub