dev
490f92935e
Test Workflow / test (push) Failing after 1m53s
- Add pyproject.toml and uv.lock for Python project with uv - Add src/__init__.py with add(), multiply(), greet() functions - Add tests/test_example.py with unit tests - Add commit-message skill for Conventional Commits - Add Gitea Actions workflow to run pytest
1.2 KiB
1.2 KiB
skill: commit-message
Follow these commit message conventions for all git commits:
Format
<type>(<scope>): <description>
[optional body]
[optional footer(s)]
Types
| Type | Description |
|---|---|
feat |
New feature |
fix |
Bug fix |
docs |
Documentation only |
style |
Code style (formatting, semicolons) |
refactor |
Code change that neither fixes nor adds |
test |
Adding or updating tests |
chore |
Maintenance, deps, build changes |
Rules
- Use imperative: "add" not "added" or "adds"
- Limit subject line to 50 chars
- Capitalize first letter of description
- No period at end of subject
- Use scope (module/file) when applicable
Breaking Changes
If change breaks backward compatibility:
- Add
BREAKING CHANGE:in footer - Use
!after type:feat!:
Examples
feat(auth): add login endpoint
fix(api): resolve null pointer in user response
docs(readme): update installation steps
feat!: migrate to v2 API
BREAKING CHANGE: auth header format changed
When to Write Body
- Explanation of "what" and "why" (not "how")
- More detail than fits in subject line
- References to issues/PRs