update claude.md (#139)

* update claude.md

* more changes

Author: abidlabs

CLAUDE.md

@@ -81,21 +81,11 @@ When given a GitHub issue to solve, follow this workflow:
 2. **Implement the solution** following the existing code patterns and conventions
 3. **Run tests** to ensure nothing is broken: `pytest`
 4. **Run linting/formatting**: `ruff check --fix --select I && ruff format`
-5. **Commit changes** with a descriptive message referencing the issue
-6. **Push the branch** to origin to automatically open a PR with a descriptive body message (1 sentence describing what the PR does and referencing the issue if applicable, e.g., "Adds a 'Log scale X-axis' checkbox to the sidebar below the X-axis dropdown, which implements log scale functionality for all plots when checkbox is enabled. Closes: #121")
+5. That's it. Never use the `git` commit command after a task is finished.
 
 ### Git Commands for Issue Workflow
 ```bash
-# Create and switch to new branch
 git checkout -b fix-issue-NUMBER
-
-# After implementing changes, add and commit
-git add -A
-git commit -m "Fix issue #NUMBER: Brief description"
-
-# Push branch and create PR with descriptive body
-git push -u origin fix-issue-NUMBER
-gh pr create --title "Fix issue #NUMBER: Brief description" --body "One sentence describing what the PR does and closes: #NUMBER"
 ```
 
 Always ensure tests pass and code is formatted before pushing.