Format:
<type> <description> (type: add | update | fix | remove | refactor)
Examples:
add user login endpoint
update dashboard layout for mobile
fix crash on empty form submission
remove deprecated payment method
refactor API response handling
Project tech-notes
add note commit-convention
add readme file
add main index
update note commit-convention
update readme file
add note replace-last
add note remove-last
add note remove-tracking
add note history-viewing
add note table-of-contents
update note replace-last
update main index
add note blog-post
update note history-viewing
add note rename-repo
update note history-viewing
rename note blog-post to note
Project misc-notes
add readme file
add note movie-review
add note video-review
add custom title
add notes movie and video review in pl
fix note video-review
update main index
fix review notes stucture
add link notes collection
That’s enough structure to stay consistent without turning commits into a discipline exercise.
Project-specific convention, adds new semantic tags used in this project
Format:
<type>: <description> (type: initial | chore | feat)
Rules:
Project cv
initial commit with cleaned data, code and styling
chore: refactored project structure
chore: established simpler structure fit for this project
feat: upload photo button
feat: page to download json schema file
feat: integrated main and schema pages
feat: move data load button to photo container and make btns style consistent
feat: tweak experience presentation, small refactor
chore: remove obsolete log data
chore: add gitignore
This keeps the system lightweight while still scaling beyond basic CRUD-style commit labels.