Naming Convention Generator
Generate consistent names for git branches and tags, feature flags, test cases, asset files, Kafka topics and Redis keys.
About this tool
Naming Convention Generator
Generate consistent names for git branches and tags, feature flags, test cases, asset files, Kafka topics and Redis keys.
Pick what you are naming, fill in the parts and copy a name that follows the convention. This page brings together 8 separate naming convention generator pages (Asset file, Feature flag, Git branch, Git tag, Kafka topic, Redis key, Test case, Terraform) so you can compare them without hunting for the right one.
How to use Naming Convention Generator
- 1
Open Naming Convention Generator on AltFTool — it loads instantly in your browser.
- 2
Choose your thing to name at the top: Asset file, Feature flag, Git branch, Git tag and 3 more. On a phone it is a drop-down list.
- 3
Fill in the naming convention generator for that thing to name; each of the 8 options keeps its own rules, data and defaults.
- 4
Read the result, then switch thing to name to compare. The page link keeps your thing to name (?v=asset-file), so you can bookmark or share it.
Why use Naming Convention Generator
All 8 in one place
Asset file, Feature flag, Git branch and the rest sit behind one picker, so switching thing to name takes a tap instead of a new search.
Built for each option
Every thing to name keeps its own rules, numbers and defaults rather than one generic template.
Shareable view
The link remembers the thing to name you picked, so a bookmark or a shared link opens straight on it.
Common use cases
- Name a batch of 30 exports for one client so they stay in shot order in Finder and Explorer.
- A platform team standardising flag names before rolling LaunchDarkly, Unleash or a homegrown flag service out to every squad
- Agreeing a team convention like feature/PROJ-123-add-login before a new project's first sprint
- Standardising on v1.2.3 style tags across a dozen microservice repositories with a regex CI can enforce
Frequently asked questions
Which thing to name options does this tool cover?
8: Asset file, Feature flag, Git branch, Git tag, Kafka topic, Redis key, Test case, Terraform. Pick one at the top of the tool; the page link updates (for example ?v=asset-file) so you can bookmark or share that exact view.
What characters are not allowed in a file name?
Windows rejects \ / : * ? " < > | and all control characters, and forbids a name that ends with a space or a period. macOS and Linux are more permissive but a forward slash is still illegal, so sticking to letters, digits, hyphens and underscores keeps a file portable everywhere.
What is a good naming convention for feature flags?
A widely used pattern is type-team-description, optionally ending with a removal date for temporary flags — for example release-payments-guest-checkout-20261001. The exact separators matter less than consistency: every flag in the codebase should encode its category, its owner and what it gates.
What is a good git branch naming convention?
The most common pattern is type/ticket-description, for example feature/PROJ-123-add-login: a type prefix (feature, bugfix, hotfix), the ticket ID, then a short kebab-case description. Slash separators make branches group into folders in tools like GitKraken and the GitHub branch list; the ticket ID lets issue trackers auto-link the branch.
Should git tags start with v?
The v prefix (v1.2.3) is the dominant convention — git's own releases use it, and tools like GoReleaser and semantic-release expect it by default. Strictly, the v is not part of the semantic version: semver.org's FAQ states v1.2.3 is not a semantic version, the version is the 1.2.3 after the prefix. Pick one style and use it everywhere.
What are the rules for Kafka topic names?
A topic name may be up to 249 characters, may contain only ASCII letters, digits, dot, underscore and hyphen, and cannot be empty, "." or "..". The 249 limit exists because the log directory on disk is named "<topic>-<partition>" and must fit inside the usual 255-character filesystem limit.
What is the naming convention for Redis keys?
The Redis documentation recommends colon-separated object-type:id schemes such as user:1000 or user:1000:followers, keeping keys short but readable. Most teams prepend an application namespace and environment (shop:prod:user:1000) so multiple apps can safely share one Redis instance.
What is the best naming convention for unit tests?
There is no single best one, but the convention has to be consistent across the repository, and the name must state the condition and the expected result rather than just the method name. Given-when-then reads best for behaviour and acceptance tests, should-style suits per-method unit tests, and UnitOfWork_StateUnderTest_ExpectedBehavior is the usual choice in Java and C# codebases where the name has to be a single identifier.