Slash commands: no more meaningless commits

It sounds like you've developed a system to leverage AI (specifically Claude) for better commit management in your version control workflow. Here's a summary of the key points and steps involved:

Key Points:

1. Custom Slash Command: You created a custom slash command /commit that guides Claude through the process of staging, committing, and writing meaningful commit messages.
2. Helper Script (bin/commit-survey): This script categorizes changes into buckets (e.g., config, docs, app) to help Claude understand which files belong together for a single commit.
3. Conventional Commits: Each commit follows the Conventional Commits guidelines, ensuring that messages are clear and consistent.

Steps Involved:

1. Run Helper Script:
   • The script runs bin/commit-survey to categorize changes into buckets like config, docs, app.
   • Example output:

     plaintext
      
     1[skip]   (none)
     2[test]   (none)
     3[db]     (none)
     4[config] config.toml
     5[docs]   content/blog/slash-commands-no-more-bad-commits.md, content

Read the full article at DEV Community

---

Want to create content about this topic? Use Nemati AI tools to generate articles, social posts, and more.