windyboy
79de88d25c
Add comprehensive slash command for generating conventional commit
messages using AI. The command analyzes staged git changes and creates
well-structured commit messages following best practices.
Features:
- Conventional commit format (type, scope, description)
- Interactive message editing and regeneration
- Context-aware analysis of git diffs
- Learning from existing commit history style
- Support for custom type and scope hints
- Multi-step workflow with user confirmation
Command supports multiple usage patterns:
- Basic: /git-commit-msg
- With hints: /git-commit-msg fix
- With context: /git-commit-msg "feat(api)"
Also updates command README with documentation for the new command.
🤖 Generated with Claude Code
117 lines
2.1 KiB
Markdown
117 lines
2.1 KiB
Markdown
# Claude Code Commands
|
|
|
|
Pre-configured commands to enhance your Claude Code + Obsidian workflow.
|
|
|
|
## Available Commands
|
|
|
|
### 🤔 thinking-partner
|
|
|
|
Engage Claude as a thinking partner for exploring complex problems.
|
|
|
|
```
|
|
/thinking-partner
|
|
```
|
|
|
|
Best for: Brainstorming, problem exploration, developing ideas
|
|
|
|
### 📥 inbox-processor
|
|
|
|
Process and organize items in your Inbox folder.
|
|
|
|
```
|
|
/inbox-processor
|
|
```
|
|
|
|
Best for: Weekly inbox cleanup, organizing captures
|
|
|
|
### 🔍 research-assistant
|
|
|
|
Conduct thorough research on any topic using your vault.
|
|
|
|
```
|
|
/research-assistant
|
|
```
|
|
|
|
Best for: Deep dives, literature reviews, knowledge synthesis
|
|
|
|
### 📅 daily-review
|
|
|
|
End-of-day review to capture progress and plan tomorrow.
|
|
|
|
```
|
|
/daily-review
|
|
```
|
|
|
|
Best for: Daily shutdown ritual, reflection
|
|
|
|
### 📊 weekly-synthesis
|
|
|
|
Create a comprehensive synthesis of the week's work.
|
|
|
|
```
|
|
/weekly-synthesis
|
|
```
|
|
|
|
Best for: Weekly reviews, pattern recognition
|
|
|
|
### 💬 git-commit-msg
|
|
|
|
AI-generated conventional commit messages from staged changes.
|
|
|
|
```
|
|
/git-commit-msg
|
|
```
|
|
|
|
Best for: Creating meaningful commit messages, maintaining clean git history
|
|
|
|
## Creating Custom Commands
|
|
|
|
1. Create a new `.md` file in this directory
|
|
2. Name it descriptively (kebab-case)
|
|
3. Structure it with:
|
|
- Clear role definition
|
|
- Specific process steps
|
|
- Expected output format
|
|
- Tips and constraints
|
|
|
|
## Using Commands
|
|
|
|
### Method 1: Direct (in Claude Code)
|
|
|
|
```
|
|
/[command-name]
|
|
```
|
|
|
|
### Method 2: Reference in Chat
|
|
|
|
```
|
|
Use the thinking-partner command to help me explore [topic]
|
|
```
|
|
|
|
### Method 3: Manual
|
|
|
|
```
|
|
Follow the instructions in .claude/commands/[command].md
|
|
```
|
|
|
|
## Tips
|
|
|
|
- Commands are just structured prompts
|
|
- Modify them based on your needs
|
|
- Combine commands for complex workflows
|
|
- Share your custom commands with the community
|
|
|
|
## Command Ideas
|
|
|
|
Consider creating commands for:
|
|
|
|
- Project retrospectives
|
|
- Meeting notes processing
|
|
- Book notes extraction
|
|
- Idea development
|
|
- Content planning
|
|
- Learning path creation
|
|
- Decision analysis
|
|
|
|
Remember: The best commands emerge from your actual workflows.
|