Reorganize Claude commands for better workflow management

Replaced generate-nx-version-plan command with three separate commands:
- git-commit: Pre-commit workflow and commit creation
- git-push: Complete workflow including push to remote
- version-plan: Dedicated version plan generation with improved guidelines

This provides clearer separation of concerns and better aligns with typical development workflows.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>

Author: phuctm97

.claude/commands/generate-nx-version-plan.md

@@ -0,0 +1,22 @@
+---
+description: Format, type check, lint, and commit all changes
+allowed-tools: Bash(pnpm -w format), Bash(pnpm exec nx run-many -t typecheck:*), Bash(pnpm exec nx run-many -t lint:*), Bash(pnpm exec nx run-many -t lint --args=--fix), Bash(git status:*), Bash(git diff:*), Bash(git branch:*), Bash(git add:*), Bash(git commit:*)
+---
+
+Run the pre-commit workflow and create a git commit with all changes.
+
+Execute the following steps in order:
+
+1. **Format code**: Run `pnpm -w format` to format all files
+2. **Type check**: Run `pnpm exec nx run-many -t typecheck` to check TypeScript types
+3. **Lint and auto-fix issues**: Run `pnpm exec nx run-many -t lint --args=--fix` to lint and auto-fix issues
+4. **Stage all changes**: Run `git add -A` to stage all changes (including any fixes from the above steps)
+5. **Review changes**: Run `git status` and `git diff` to review what will be committed
+6. **Create commit**: Generate an appropriate commit message based on the changes and create the commit
+
+For the commit message:
+- Keep it concise and descriptive
+- Focus on the "why" rather than the "what"
+- DO NOT use conventional commit prefixes (no "fix:", "feat:", "chore:", etc.)
+
+If any of the formatting, type checking, or linting steps fail, attempt to fix the issues. After fixing the issues or making any changes manually, repeat the entire process from step 1 to ensure everything is in order before committing.

.claude/commands/git-commit.md

@@ -0,0 +1,25 @@
+---
+description: Format, type check, lint, commit all changes, and push to remote
+allowed-tools: Bash(pnpm -w format), Bash(pnpm exec nx run-many -t typecheck:*), Bash(pnpm exec nx run-many -t lint:*), Bash(pnpm exec nx run-many -t lint --args=--fix), Bash(git status:*), Bash(git diff:*), Bash(git branch:*), Bash(git add:*), Bash(git commit:*), Bash(git push:*)
+---
+
+Run the pre-commit workflow, create a git commit with all changes, and push to the remote repository.
+
+Execute the following steps in order:
+
+1. **Format code**: Run `pnpm -w format` to format all files
+2. **Type check**: Run `pnpm exec nx run-many -t typecheck` to check TypeScript types
+3. **Lint and auto-fix issues**: Run `pnpm exec nx run-many -t lint --args=--fix` to lint and auto-fix issues
+4. **Stage all changes**: Run `git add -A` to stage all changes (including any fixes from the above steps)
+5. **Review changes**: Run `git status` and `git diff` to review what will be committed
+6. **Create commit**: Generate an appropriate commit message based on the changes and create the commit
+7. **Push to remote**: Check the current branch with `git branch --show-current` and push the changes with `git push`
+
+For the commit message:
+- Keep it concise and descriptive
+- Focus on the "why" rather than the "what"
+- DO NOT use conventional commit prefixes (no "fix:", "feat:", "chore:", etc.)
+
+If any of the formatting, type checking, or linting steps fail, attempt to fix the issues. After fixing the issues or making any changes manually, repeat the entire process from step 1 to ensure everything is in order before committing.
+
+If the push fails (e.g., due to remote changes), report the errors to the user for resolution.

.claude/commands/git-push.md

@@ -0,0 +1,70 @@
+---
+description: Generate an Nx version plan based on current git changes
+allowed-tools: Bash(git status:*), Bash(git diff:*), Read(.nx/version-plans/**), Edit(.nx/version-plans/**)
+---
+
+Analyze the current git changes (both staged and unstaged) and generate a new Nx version plan file.
+
+First, check `git status` and `git diff` to understand what has changed. If there are no changes, inform the user that no version plan is needed.
+
+Then, check existing version plans in `.nx/version-plans/` to ensure you're not creating a duplicate or similar plan.
+
+Analyze the changes to determine:
+1. The appropriate semantic version bump:
+   - **patch**: Bug fixes, typo corrections, internal refactors that don't affect functionality
+   - **minor**: New features, enhancements, non-breaking improvements
+   - **major**: Breaking changes, API modifications, removal of features
+2. A concise, single-line changelog entry
+
+Create the version plan file in `.nx/version-plans/` with a filename that briefly summarizes the change (using kebab-case).
+
+The file format should be:
+```markdown
+---
+__default__: version-type
+---
+
+Single line changelog entry describing the changes
+```
+
+Examples:
+
+1. Bug fix (patch):
+   - Filename: `fix-memory-leak-in-parser.md`
+   - Content:
+   ```markdown
+   ---
+   __default__: patch
+   ---
+
+   Fix memory leak in parser when handling large files
+   ```
+
+2. New feature (minor):
+   - Filename: `add-authentication-feature.md`
+   - Content:
+   ```markdown
+   ---
+   __default__: minor
+   ---
+
+   Add authentication feature with OAuth support
+   ```
+
+3. Breaking change (major):
+   - Filename: `remove-deprecated-api-methods.md`
+   - Content:
+   ```markdown
+   ---
+   __default__: major
+   ---
+
+   Remove deprecated API methods from v1.x
+   ```
+
+Important:
+- Always use `__default__` since this repository releases the same version for all projects
+- The changelog entry must be a single line without bullet points or multiple paragraphs
+- If there are multiple unrelated changes, create separate version plans for each
+- The filename should be descriptive, unique, and clearly indicate what changed
+- Avoid creating plans for changes that already have similar plans in the directory