git-conventionslisted

# Git Commit and Version Control Conventions ## Commit Message Format This project follows the [Conventional Commits](https://www.conventionalcommits.org/) specification for commit messages. This format enables automatic changelog generation, version bumping, and better collaboration. ### Structure ```text <type>(<scope>): <subject> [optional body] [optional footer(s)] ``` ### Type The type must be one of the following: - `feat` - A new feature for the user - `fix` - A bug fix - `docs` - Documentation only changes - `style` - Changes that don't affect the meaning of code (white-space, formatting, etc.) - `refactor` - Code change that neither fixes a bug nor adds a feature - `perf` - Code change that improves performance - `test` - Adding missing tests or correcting existing tests - `build` - Changes that affect the build system or external dependencies - `ci` - Changes to CI configuration files and scripts - `chore` - Other changes that don't modify src or test files - `revert` - Reverts a previous commit ### Scope Infer scope from staged file paths. Use the workspace **directory name**, not the npm package name (`packages/cli` is `cli`, not `transcripts-mcp`). Scope is optional; omit it or use `repo` for repo-wide work. Multiple scopes are allowed when each is a valid workspace or meta scope (`feat(mcp,search):`). **Apps:** - `mcp` - stdio MCP server - `www` - Marketing site **Packages:** - `core` - Types, adapter contract, jsonl reader - `adapters` - Cursor,