Built-in Modules
git-recap doesn't just list your commits—it intelligently categorizes them into logical modules. This allows your team to quickly understand the *type* of work you accomplished during your standup.
The Grouping Algorithm
When git-recap scans your repository, it analyzes the commit subject line. It first checks for standard Conventional Commit prefixes (like feat: or fix:). If found, it instantly categorizes the commit and gracefully strips the prefix from the output to keep your standup clean.
If no conventional prefix is found, it falls back to a smart keyword-matching system, searching for words like "add", "resolve", or "update" to place the commit in the best possible bucket.
Categories Overview
Features
New functionality or additions to the codebase.
Example Commits:
- feat: add user authentication
- Add new dashboard widget
Fixes
Bug fixes and error resolutions.
Example Commits:
- fix: resolve null pointer in login
- Patch memory leak
Docs
Documentation updates.
Example Commits:
- docs: update readme with setup instructions
- Add docstrings to API router
Refactors
Code structure changes without behavior change.
Example Commits:
- refactor: extract authentication service
- Cleanup dead code
Tests
Adding or updating tests.
Example Commits:
- test: add coverage for utils
- Update snapshot tests
Performance
Performance optimizations.
Example Commits:
- perf: lazy load images on homepage
- Optimize database query
Chores
Maintenance, dependencies, and build tasks.
Example Commits:
- chore: bump react to 18.2.0
- Update github actions workflow
The "Other" Bucket
What happens when a commit defies categorization? If git-recap cannot confidently place a commit into one of the primary modules, it is safely stored in the Other category at the bottom of your summary. Nothing is ever lost or hidden.