Skip to content
TheChatArchiveThe Chat Archive
Amazon Novaamazon-nova-experimental-chat-05-14· AmazonHugging Face LMArena Human Preference 140K

Can you create the worst possible git commit title and description?

From a Chatbot Arena battleThe same person sent this prompt to two anonymous models at once. Compare it with Kimikimi-k2-0711-preview’s answer.
  1. User

    Can you create the worst possible git commit title and description?

  2. Amazon Nova Assistant

    Certainly! Here's an example of the worst possible git commit title and description:

    Commit Title:

    stuff

    Commit Description:

    idk some changes lol
    - did a thing
    - fixed stuff
    - more stuff
    - who knows
    - hmm
    - whatever
    - changed some files
    - maybe it works?
    - oops
    - yolo
    - random edits
    - hopefully this is right
    - just testing
    - meh
    

    Breakdown of Why This is the "Worst":

    1. Vague Title:

      • "stuff": Provides absolutely no information about what the commit entails. It's completely generic and uninformative.
    2. Non-Descriptive Description:

      • "idk some changes lol": Starts with “idk” (I don’t know) which immediately indicates a lack of understanding or care about the changes. “lol” is inappropriate for a professional commit message.
      • Bullet Points:
        • "did a thing": Extremely vague. Offers no insight into what was actually done
        • "fixed stuff": Doesn't specify what was fixed. “stuff” is not a descriptive term
        • “more stuff”: Even more vague than “stuff”
        • "who knows": Admits uncertainty, which is terrible for a commit message that should document changes precisely.
        • "hmm": Indicates indecision or lack of thought.
        • “whatever”: Shows a lack of care or interest.
        • "changed some files": Doesn't specify which files or what changes were made.
        • "maybe it works?": Indicates uncertainty about whether the changes are correct or effective.
        • "oops": Admits to a mistake but doesn't explain what the mistake was or how it was addressed.
        • "yolo": “You Only Live Once” is inappropriate and unprofessional for a commit message.
        • "random edits": Implies that changes were made without a clear purpose or plan.
        • "hopefully this is right": More uncertainty; a commit message should confidently describe completed, correct changes.
        • "just testing": Doesn’t explain what is being tested or the purpose of the test.
        • “meh”: Demonstrates apathy
    3. Lack of Structure:

      • There is no clear structure or format. Professional commit messages often follow conventions like the Conventional Commits specification, which this message completely ignores.
    4. Inappropriate Tone:

      • The use of slang (“lol”, “yolo”) and informal language (“idk”, “meh”) is highly inappropriate for a professional codebase. Commit messages should maintain a professional tone.

    This commit title and description provide no valuable information to anyone reviewing the project history, making it essentially useless and exemplifying the “worst” possible commit message.

Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.