<!-- Generated by SpecStory, Markdown v2.0.0 -->

<!-- cursor Session 97b9e83f-b446-4aed-807c-d34788ce8249 (2025-11-15 15:42Z) -->

# Good git commit workflow for app (2025-11-15 15:42Z)

_**User (2025-11-15 07:35Z)**_

for this app in particular, whats a good workflow for commiting changes to git

---

_**Agent (model default, mode Ask)**_

<think><details><summary>Thought Process</summary>
**Checking commit workflow instructions**</details></think>

---

<tool-use data-tool-type="read" data-tool-name="read_file">
<details><summary>Tool use: **read_file** • Read file: /home/nicholai/Documents/dev/multi-agent_chat_interface/.cursor/commands/commit-changes.md</summary>

</details>
</tool-use>

---

<think><details><summary>Thought Process</summary>
**Preparing final guidance response**</details></think>

---

Suggested git workflow for this repo:

- **Stage prep**: Review `git status` to understand dirty files, then inspect diffs per file (`git diff path/to/file`) to confirm only the intended changes go in.
- **Quality gates**: Run `pnpm lint`, relevant tests (`pnpm test`, or targeted suites), and—if UI work—manually verify in browser per UI Development Protocol.
- **Summaries**: Update docs or comments if behavior changed; keep `CHANGELOG` or task ticket notes in sync if you use them.
- **Commit message**: Compose conventional, task-oriented messages (e.g., `feat: add pinned agent reordering animation`) before committing with `git commit -am "...` or `git commit` after staging via `git add`.
- **Final check**: Re-run `git status` to confirm a clean tree, then push or open a PR.

---

