Files
_template/COMMITS.md
T
2026-06-30 18:57:01 +03:00

2.4 KiB

Commit conventions

Format: [prefix] description or [prefix:scope] description. Use the imperative mood. The scope is optional and names an instrument or section, e.g. [mix:vox], [track:gtr].

Prefixes

Prefix When to use Example
sketch Early phase: composition, arrangement and mix are still intertwined [sketch] Rough verse and chorus, draft balance
comp Material: melody, harmony, structure [comp] Rewrite the bridge, drop the pre-chorus
arr Arrangement, instrumentation [arr] Add string pad to the chorus
track Recording live audio [track:gtr] Solo guitar (Artem), 3 takes
midi MIDI and virtual instruments [midi] Verse drums, fix the groove
edit Processing recordings: comping, timing, tuning, cleanup [edit:vox] Comp the lead, clean up breaths
mix Mixing [mix:vox] De-esser on lead, +1.5 dB in chorus
master Mastering (the process) [master] Limiter, target -9 LUFS
export Emitting files into Out/ (audio, PDF) [export] Master v1, instrumental, stems
score Notation source (.mscz) [score] Solo guitar part, clean copy
asset Non-audio resources: presets, FX chains, cover art [asset] Cover v2, master-bus preset
docs Documentation, README [docs] Update the description
chore Repo plumbing: structure, gitignore/gitattributes, LFS [chore] Track .mscz with LFS
fix Fixes: bad take, clipping, wrong file, revert [fix] Remove clipping at 2:13, re-export stem

Core day-to-day flow: sketch -> comp/arr -> track/midi/edit -> mix -> master -> export. Rarely used: fix, chore, asset.