instrument-commit-message

To write a git commit message for the Instrument monorepo, use a scope-first style that identifies the specific project area like studio or workspace, followed by a concise subject to ensure maintainable communication.

Scope identification in version control commit messages extracts the specific affected module, such as studio or dx, from the Instrument monorepo structure to prefix the commit subject for clear project tracking.

Format a monorepo commit message by placing the scope identifier first, followed by a colon and a concise informative subject, such as "ui: improve responsiveness of sidebar".

Yes, generating a scope-first commit message requires knowledge of the Instrument project's scopes and structure to accurately identify the correct module prefix like workspace or dx.

The best way to maintain clear communication in monorepo commit history is to standardize commit messages using a scope-first format, ensuring every change clearly identifies its affected area and intent.