From c867d7db63ba9386d7929b07b3b38ec9308bf9d2 Mon Sep 17 00:00:00 2001 From: Sridhar Ratnakumar Date: Mon, 29 Sep 2025 17:19:19 -0400 Subject: [PATCH] claude-code/command/c: Add component prefix guidelines for commit messages --- modules/home/claude-code/commands/c.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/modules/home/claude-code/commands/c.md b/modules/home/claude-code/commands/c.md index 7f91722..310752d 100644 --- a/modules/home/claude-code/commands/c.md +++ b/modules/home/claude-code/commands/c.md @@ -32,11 +32,13 @@ This command commits the current changes to git. - Analyze the git diff to understand what changed - Create a concise, descriptive commit message that explains the purpose of the changes - Focus on the "what" and "why" rather than generic descriptions +- Prefix the commit message with component (and subcomponent if it exists, separated by /), e.g., `claude-code/command/c: Include component path in commit message` - Examples of good vs bad messages: - - Good: "Add tmux configuration with custom key bindings" + - Good: "tmux: Add configuration with custom key bindings" - Bad: "Update home configuration" - - Good: "Fix broken SSH agent forwarding in development environment" + - Good: "ssh: Fix broken agent forwarding in development environment" - Bad: "Update configuration files" + - Good: "claude-code/command/c: Add commit message generation guidelines" **Prerequisites**: - Must be in a git repository