Skip to content

Standardize bang names based on new naming spec#403

Draft
FaFre wants to merge 5 commits intokagisearch:mainfrom
FaFre:uniform_names
Draft

Standardize bang names based on new naming spec#403
FaFre wants to merge 5 commits intokagisearch:mainfrom
FaFre:uniform_names

Conversation

@FaFre
Copy link
Copy Markdown

@FaFre FaFre commented Apr 21, 2026

Currently, many bang names do not follow a specific pattern, and their names often fail to describe their actual behavior. This makes discovering the correct bang difficult when searching by name. Since I run a search on the names, this lead to a lot of false positives and confusion.

For example, the following bang applies a Spanish language tag, but you wouldn't know it just from looking at the name:

{
    "s": "duckduckgo",
    "d": "duckduckgo.com",
    "t": "ddg-es",
    "u": "https://duckduckgo.com/?q={{{s}}}&kl=xl-es&kad=es_ES&ia=about",
    "c": "Online Services",
    "sc": "Search (non-US)"
  }

To fix this, I created a naming specification to ensure bang names accurately reflect their function (such as including language or region tags): https://github.com/FaFre/bangs/blob/main/WEBSITE_NAMING_SPEC.md

I used an LLM to apply this spec across the repository in small batches. Therefore all of the renames are done by LLM and are not manually reviewed.

I am not sure if a PR of this size and impact is something that is welcomed to merge, so please let me know if there is interest. I could do this since I had a lot of tokens to burn. Another run (after maybe changes to the spec) will be not possible from my side.

Edit: I forgot to mention the PR also includes some removals of duplicate or nearly identical bangs...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant