Skip to content

Commit a3a7ce6

Browse files
kingRayhanclaude
andcommitted
feat: add Claude configuration directory
🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <[email protected]>
1 parent 130c549 commit a3a7ce6

File tree

1 file changed

+36
-0
lines changed

1 file changed

+36
-0
lines changed

.claude/commands/gc.md

Lines changed: 36 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,36 @@
1+
# Git Commit Helper
2+
3+
You are tasked with analyzing all unstaged git files and creating an appropriate commit message, then executing the commit.
4+
5+
Follow these steps:
6+
7+
1. **Check git status** to see all unstaged files
8+
2. **Show git diff** to understand the changes being made
9+
3. **Review recent commits** (last 5) to understand the project's commit message style
10+
4. **Analyze the changes** and determine:
11+
12+
- Type of changes (feat, fix, refactor, docs, etc.)
13+
- Main purpose and impact
14+
- Any breaking changes or important notes
15+
16+
5. **Draft a commit message** that:
17+
18+
- Follows the project's existing style
19+
- Uses conventional commit format if the project uses it
20+
- Summarizes the "why" rather than just the "what"
21+
- Is concise but descriptive
22+
23+
6. **Execute the commit**:
24+
- Add all unstaged files to staging
25+
- Create the commit with the drafted message
26+
- Verify the commit succeeded
27+
28+
**Important guidelines:**
29+
30+
- Never commit if there are no changes
31+
- Check for sensitive information before committing
32+
- Follow the project's existing commit message patterns
33+
- Include the Claude Code attribution in commit messages
34+
- Be concise and focus on the main changes
35+
36+
$ARGUMENTS can be used to provide additional context or specific instructions for the commit message.

0 commit comments

Comments
 (0)