commit
Stage and commit git changes with conventional prefixes. Use when the user asks to commit, save changes, write a commit message, or push staged work to the repository.
Source facts
- Repository
- lsegal/aviary
- Last source activity
- May 21, 2026 at 17:28
- Detected SKILL.md language
- English
- Stars
- 12
- Forks
- 5
Install options
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Review the source files
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Showing SKILL.md
SKILL.md
Source instructions · Read-only preview- name
- commit
- description
- Stage and commit git changes with conventional prefixes. Use when the user asks to commit, save changes, write a commit message, or push staged work to the repository.
Group changed files into logical commits by what they changed. Each commit uses a conventional prefix:
- `bug:` — bug fixes
- `feature:` — new features
- `test:` — test-only changes
- `chore:` — maintenance, refactoring, dependencies
## Workflow
1. Run `git status` and `git diff --stat` to identify all changed files
2. Group related changes (e.g., all files for one feature together)
3. For each group:
- Stage files: `git add <file1> <file2>`
- Review staged diff: `git diff --staged --stat`
- Commit: `git commit -m "feature: add calendar sync endpoint"`
4. Keep subject lines under 72 characters; add detail in the commit body if needed
## Examples
```
bug: fix nil pointer in envelope thread lookup
feature: add Drive file search to gogcli skill
test: add e2e tests for calendar event creation
chore: update Go dependencies
```
View on GitHub