Bad Commit Messages? Here's What I Do Instead (Copilot)

Automate Conventional Commits in VS Code using GitHub Copilot Custom Instructions. Get the exact prompt I use to fix bad commit messages without losing control (Principal Engineer Workflow). 📂 Get my Custom Instruction Prompt (GitHub Repo): 🔗 https://github.com/ikcode-dev/copilot-kit --- Bad commit messages are everywhere—vague, misleading, or missing the “why.” And with coding agents auto-committing, it’s getting worse. My workflow stops this chaos while keeping the rule that matters most: AI-assisted ≠ autopilot. Copilot drafts the message. You approve the commit. ✅ What you'll learn: - Why commit messages fail (and how AI can amplify the problem) - How to configure VS Code & Copilot for better commits - The specific prompt I use for Conventional Commits - A live demo: Refactoring code and generating perfect commits instantly ✅ Resources & Links: - ⭐️ Copilot Kit Repo (The Prompt): https://github.com/ikcode-dev/copilot-kit - Sub-Sync Project (Demo Code): https://github.com/ikcode-dev/subsync - Follow me on BlueSky: https://bsky.app/profile/ikcode.dev ⌚ Timestamps: 00:00 Why Commit Messages Fail (Especially with AI) 00:17 AI‑Assisted ≠ Autopilot: My Commit Rule 00:47 Setup: Copilot Custom Instructions for Commit Messages (VS Code) 03:09 Demo: Conventional Commits Generated by Copilot 06:50 My Workflow Recap + Next Video ❓ Question for you: Do you let your coding agent commit automatically—or do you stay in the loop? Drop a comment with your workflow. ➡️ Up Next: The full AI-Assisted Programming workflow for professional teams (Specs + Copilot + Reviews). #GitHubCopilot #ConventionalCommits #VSCode #SoftwareEngineering #DevOps