Auto-generates concise git commit messages after file modifications, following best practices for clear version control history.
Automatically generates clear, concise git commit messages after file modifications. This skill helps maintain consistent and meaningful version control history by providing descriptive commit messages that explain what changed without requiring code review.
When you modify files in your codebase, this skill instructs GitHub Copilot to automatically generate an appropriate commit message that:
After completing any action that results in modifying a file:
1. **Analyze the modification** - Review what changed in the file(s)
2. **Generate a commit message** that:
- Is concise yet descriptive
- Explains WHAT changed and WHY (when relevant)
- Uses imperative mood (e.g., "Add feature" not "Added feature")
- Is clear enough to understand without viewing the code
3. **Output only the commit message** - Do not provide:
- Terminal commands (no `git commit -m`)
- Code fences or formatting
- Explanations or additional text
- Just the commit message itself
**Example 1: Feature Addition**
```
User modifies authentication.ts to add OAuth support
Generated message: "Add OAuth authentication support with Google and GitHub providers"
```
**Example 2: Bug Fix**
```
User fixes a null pointer error in user profile component
Generated message: "Fix null pointer exception when loading user profile without avatar"
```
**Example 3: Refactoring**
```
User extracts database logic into separate service
Generated message: "Refactor database queries into dedicated service layer"
```
**Example 4: Configuration Update**
```
User updates environment variables in config file
Generated message: "Update API endpoints and timeout values in production config"
```
Leave a review
No reviews yet. Be the first to review this skill!
# Download SKILL.md from killerskills.ai/api/skills/github-copilot-commit-message-generator/raw