| name | git-conventions |
| description | Apply when committing code, creating branches, or preparing pull requests. Covers conventional commit format, branch naming, co-author attribution, and pre-commit checklist. |
Git Conventions
Commit Message Format
Use conventional commits:
feat:- New featuresfix:- Bug fixesrefactor:- Code refactoringdocs:- Documentation changesstyle:- Formatting changestest:- Test additions/changeschore:- Maintenance tasks
Commit Template
git commit -m "feat: add new feature description
- Detailed change 1
- Detailed change 2
Co-authored-by: Ona <no-reply@ona.com>"
Branch Naming
git checkout -b feature/your-feature-name
git checkout -b fix/bug-description
git checkout -b refactor/area-being-refactored
Workflow
- Create feature branch from main
- Make changes with conventional commits
- Push and create PR:
git push -u origin feature/your-feature-name gh pr create --title "feat: your feature title" --body "Description of changes"
Pre-commit Checklist
- Run
git statusto see all changes - Run
git diffto review modifications - Run
git log --oneline -5to understand commit style - Only stage files relevant to current task
- Do not commit files modified before task began unless related
- Add co-author line
Important Rules
- Never commit or push unless explicitly asked
- Single commit permission does not grant future permissions
- For PRs, ensure you're on a non-default branch