{
  "id": 7888706,
  "title": "How I Built a VS Code Extension That Solves Bad Commit Messages (No AI Required)",
  "url": "https://urgent.news/2026/09/16/how-i-built-a-vs-code-extension-that-solves-bad-commit-messages-no-ai",
  "topic": "ai",
  "section": "AI",
  "published": "2026-09-16T21:55:57.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/chekarda_ali_c14d11faf19c/how-i-built-a-vs-code-extension-that-solves-bad-commit-messages-no-ai-required-411n"
  },
  "original_language": "en",
  "account": "Developers often commit code with vague messages like \"fix\" or \"update\". This makes it difficult to understand the changes made later on. Writing good commit messages requires reviewing the code changes, deciding on the appropriate type, and crafting a clear subject line. It's a tedious process that developers would rather avoid.\n\nTo simplify this, I created Git Commit Genius, a VS Code extension that automatically generates professional commit messages. Here's how it works: first, stage the files you want to commit with \"git add .\". Then press Ctrl+Shift+C to bring up the extension. It provides four smart suggestions to choose from. Once you pick one, you can commit with just one click.\n\nThe extension offers several benefits. It works completely offline, so there's no need for AI or external API calls. It adheres to the Conventional Commits standard. The extension has four actions: \"Commit now\" to directly commit with the selected suggestion, \"Copy as git command\" to copy the commit command, \"Copy message\" to copy the commit message, or \"Set in Git panel\" to set the commit message directly in the Git panel. It supports over 15 different file types.\n\nThe reason behind the absence of AI is simple. While AI generators exist, they come with costs, require an internet connection, send your code to external servers, and can be slow. My tool, on the other hand, uses pattern matching and file analysis to generate suggestions locally and instantly.\n\nIf you're interested in trying it out, you can do so at https://payhip.com/b/3QYiN. And for any feedback or feature requests, you can reach out to me. Up next, I plan to introduce custom commit templates, multi-language support, and team-shared configurations.",
  "summary": "Every developer has done it. You finish some code, open the terminal, and write: git commit -m \"fix\" Or worse: git commit -m \"update\" Months later, you look at your history and have no idea what changed. The Problem Good commit messages take time. You have to: Review the diff Think about the format Choose the right type (feat/fix/refactor) Write a clear subject line It's not hard — it's just…",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}