Evan Reichard
72ddbb288e
- Update llama.cpp from b7789 to b7867 - Update llama-swap from v182 to v186 - Add OpenCode conventional commit command configuration - Add moonshotai Kimi-K2.5 model to llama-swap
1.2 KiB
1.2 KiB
description, agent
| description | agent |
|---|---|
| Create a conventional commit from git changes | build |
Run git commands to ensure all changes are staged, then generate a conventional commit message based on the diff and create the commit.
Steps:
- Add all files (including untracked) using
git add -A - Show the current diff with
git diff --cachedandgit diff --staged - Analyze the changes and create a conventional commit message following the format:
- Type (feat, fix, docs, style, refactor, test, chore, etc.)
- Scope (optional, e.g., "runtime", "functions")
- Subject (brief description, imperative mood)
- Body (detailed explanation, optional)
- Execute
git commit -m "message"with the generated message - Show the commit result with
git log -1 --stat
Conventional commit format:
<type>(<scope>): <subject>
<body>
<footer>
Common types:
- feat: New feature
- fix: Bug fix
- docs: Documentation changes
- style: Code style changes (formatting, semicolons, etc.)
- refactor: Code refactoring (neither bug fix nor feature)
- test: Adding or updating tests
- chore: Maintenance tasks
- perf: Performance improvements
- ci: CI/CD changes
- build: Build system or dependencies
- revert: Revert a previous commit