zcf 2.8.2 → 2.9.0

package/README.md

@@ -250,6 +250,7 @@ Enter your choice: _
 ? Select workflows to install (space to select, enter to confirm)
   ❯ ◉ Six Steps Workflow (workflow) - Complete 6-phase development process
     ◉ Feature Planning and UX Design (feat + planner + ui-ux-designer) - Structured feature development
+    ◉ Git Commands (commit + rollback + cleanBranches) - Streamlined Git operations
     ◉ BMAD-Method Extension Installer - Enterprise agile development workflow
 
 ✔ Installing workflows...
@@ -257,6 +258,9 @@ Enter your choice: _
   ✔ Installed command: zcf/feat.md
   ✔ Installed agent: zcf/plan/planner.md
   ✔ Installed agent: zcf/plan/ui-ux-designer.md
+  ✔ Installed command: zcf/git/git-commit.md
+  ✔ Installed command: zcf/git/git-rollback.md
+  ✔ Installed command: zcf/git/git-cleanBranches.md
   ✔ Installed command: zcf/bmad-init.md
 ✔ Workflow installation successful
 
@@ -388,6 +392,10 @@ zcf/
 
 - **Feature Development** (`/feat`): Structured new feature development
 - **Workflow** (`/workflow`): Complete six-phase development workflow
+- **Git Commands**: Streamlined Git operations
+  - `/git-commit`: Smart commit with automatic staging and message generation
+  - `/git-rollback`: Safely rollback to previous commits with backup
+  - `/git-cleanBranches`: Clean up merged branches and maintain repository hygiene
 - **BMad Workflow** (`/bmad-init`): Initialize BMad workflow for enterprise development
   - Supports both greenfield (new projects) and brownfield (existing projects)
   - Provides comprehensive templates for PRDs, architecture docs, and user stories

package/dist/chunks/simple-config.mjs

@@ -8,7 +8,6 @@ import { exec } from 'tinyexec';
 import { exec as exec$1 } from 'child_process';
 import { promisify } from 'util';
 import ora from 'ora';
-import prompts$1 from 'prompts';
 import { readFile as readFile$1, writeFile as writeFile$1, mkdir } from 'fs/promises';
 import { join as join$1 } from 'path';
 import { homedir as homedir$1 } from 'os';
@@ -19,7 +18,7 @@ import { promisify as promisify$1 } from 'node:util';
 import { homedir, platform } from 'node:os';
 import { join as join$2 } from 'node:path';
 
-const version = "2.8.2";
+const version = "2.9.0";
 const homepage = "https://github.com/UfoMiao/zcf";
 
 const common$1 = {
@@ -245,7 +244,8 @@ const workflow$1 = {
   workflowOption: {
     featPlanUx: "\u529F\u80FD\u89C4\u5212\u548C UX \u8BBE\u8BA1 (feat + planner + ui-ux-designer)",
     sixStepsWorkflow: "\u516D\u6B65\u5DE5\u4F5C\u6D41 (workflow)",
-    bmadWorkflow: "BMAD-Method \u6269\u5C55\u5B89\u88C5\u5668 (\u652F\u6301\u654F\u6377\u5F00\u53D1\u5DE5\u4F5C\u6D41)"
+    bmadWorkflow: "BMAD-Method \u6269\u5C55\u5B89\u88C5\u5668 (\u652F\u6301\u654F\u6377\u5F00\u53D1\u5DE5\u4F5C\u6D41)",
+    gitWorkflow: "Git \u6307\u4EE4 (commit + rollback + cleanBranches)"
   },
   // BMAD workflow
   bmadInitPrompt: "\u2728 \u8BF7\u5728\u9879\u76EE\u4E2D\u8FD0\u884C /bmad-init \u547D\u4EE4\u6765\u521D\u59CB\u5316\u6216\u66F4\u65B0 BMAD-Method \u6269\u5C55",
@@ -706,7 +706,8 @@ const workflow = {
   workflowOption: {
     featPlanUx: "Feature Planning and UX Design (feat + planner + ui-ux-designer)",
     sixStepsWorkflow: "Six Steps Workflow (workflow)",
-    bmadWorkflow: "BMAD-Method Extension Installer (Agile Development Workflow)"
+    bmadWorkflow: "BMAD-Method Extension Installer (Agile Development Workflow)",
+    gitWorkflow: "Git Commands (commit + rollback + cleanBranches)"
   },
   // BMAD workflow
   bmadInitPrompt: "\u2728 Please run /bmad-init command in your project to initialize or update BMAD-Method extension",
@@ -2153,11 +2154,11 @@ async function updateCcr(scriptLang, force = false) {
     }
     console.log(ansis.cyan(format(i18n.updater.currentVersion, { version: currentVersion || "" })));
     console.log(ansis.cyan(format(i18n.updater.latestVersion, { version: latestVersion })));
-    const { confirm } = await prompts$1({
+    const { confirm } = await inquirer.prompt({
       type: "confirm",
       name: "confirm",
       message: format(i18n.updater.confirmUpdate, { tool: "CCR" }),
-      initial: true
+      default: true
     });
     if (!confirm) {
       console.log(ansis.gray(i18n.updater.updateSkipped));
@@ -2203,11 +2204,11 @@ async function updateClaudeCode(scriptLang, force = false) {
     }
     console.log(ansis.cyan(format(i18n.updater.currentVersion, { version: currentVersion || "" })));
     console.log(ansis.cyan(format(i18n.updater.latestVersion, { version: latestVersion })));
-    const { confirm } = await prompts$1({
+    const { confirm } = await inquirer.prompt({
       type: "confirm",
       name: "confirm",
       message: format(i18n.updater.confirmUpdate, { tool: "Claude Code" }),
-      initial: true
+      default: true
     });
     if (!confirm) {
       console.log(ansis.gray(i18n.updater.updateSkipped));
@@ -2411,12 +2412,24 @@ const WORKFLOW_CONFIGS = [
     category: "plan",
     outputDir: "feat"
   },
+  {
+    id: "gitWorkflow",
+    nameKey: "workflowOption.gitWorkflow",
+    descriptionKey: "workflowDescription.gitWorkflow",
+    defaultSelected: true,
+    order: 3,
+    commands: ["git-commit.md", "git-rollback.md", "git-cleanBranches.md"],
+    agents: [],
+    autoInstallAgents: false,
+    category: "git",
+    outputDir: "git"
+  },
   {
     id: "bmadWorkflow",
     nameKey: "workflowOption.bmadWorkflow",
     descriptionKey: "workflowDescription.bmadWorkflow",
     defaultSelected: true,
-    order: 3,
+    order: 4,
     commands: ["bmad-init.md"],
     agents: [],
     autoInstallAgents: false,
@@ -2528,7 +2541,7 @@ async function installWorkflowWithDependencies(config, configLang, scriptLang) {
     console.log(ansis.green(`\u2714 ${workflowName} ${i18n.workflow.workflowInstallSuccess}`));
     if (config.id === "bmadWorkflow") {
       console.log(ansis.cyan(`
-${i18n.bmad.bmadInitPrompt}`));
+${i18n.workflow.bmadInitPrompt}`));
     }
   } else {
     console.log(ansis.red(`\u2717 ${workflowName} ${i18n.workflow.workflowInstallError}`));

package/dist/cli.mjs

@@ -13,7 +13,6 @@ import 'pathe';
 import 'dayjs';
 import 'node:url';
 import 'ora';
-import 'prompts';
 import 'fs/promises';
 import 'path';
 import 'os';
@@ -747,7 +746,7 @@ async function update(options = {}) {
     }
     const aiOutputLang = await resolveAiOutputLanguage(scriptLang, options.aiOutputLang, zcfConfig);
     console.log(ansis.cyan(`
-${i18n.workflow.updatingPrompts}
+${i18n.configuration.updatingPrompts}
 `));
     await updatePromptOnly(configLang, scriptLang, aiOutputLang);
     await selectAndInstallWorkflows(configLang, scriptLang);

package/dist/index.mjs

@@ -9,7 +9,6 @@ import 'tinyexec';
 import 'child_process';
 import 'util';
 import 'ora';
-import 'prompts';
 import 'fs/promises';
 import 'path';
 import 'os';

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "zcf",
   "type": "module",
-  "version": "2.8.2",
+  "version": "2.9.0",
   "description": "Zero-Config Claude-Code Flow - One-click configuration tool for Claude Code",
   "license": "MIT",
   "homepage": "https://github.com/UfoMiao/zcf",
@@ -21,7 +21,6 @@
     "templates"
   ],
   "dependencies": {
-    "@types/prompts": "^2.4.9",
     "@types/semver": "^7.7.0",
     "ansis": "^3.17.0",
     "cac": "^6.7.14",
@@ -30,7 +29,6 @@
     "inquirer": "^12.9.0",
     "ora": "^8.2.0",
     "pathe": "^2.0.3",
-    "prompts": "^2.4.2",
     "semver": "^7.7.2",
     "tinyexec": "^1.0.1"
   },

package/templates/en/workflow/git/commands/git-cleanBranches.md

@@ -0,0 +1,101 @@
+---
+description: Safely find and clean up merged or stale Git branches with dry-run mode and custom base/protected branches support
+allowed-tools: Read(**), Exec(git fetch, git config, git branch, git remote, git push, git for-each-ref, git log), Write()
+argument-hint: [--base <branch>] [--stale <days>] [--remote] [--force] [--dry-run] [--yes]
+# examples:
+#   - /git-cleanBranches --dry-run
+#   - /git-cleanBranches --base release/v2.1 --stale 90
+#   - /git-cleanBranches --remote --yes
+---
+
+# Claude Command: Clean Branches
+
+This command **safely** identifies and cleans up **merged** or **stale** Git branches.
+Runs in **read-only preview (`--dry-run`)** mode by default, requiring explicit instructions to perform deletions.
+
+---
+
+## Usage
+
+```bash
+# [Safest] Preview branches to be cleaned without executing any deletions
+/git-cleanBranches --dry-run
+
+# Clean local branches merged to main and inactive for over 90 days (requires individual confirmation)
+/git-cleanBranches --stale 90
+
+# Clean local and remote branches merged to release/v2.1 (auto-confirm)
+/git-cleanBranches --base release/v2.1 --remote --yes
+
+# [Dangerous] Force delete an unmerged local branch
+/git-cleanBranches --force outdated-feature
+```
+
+### Options
+- `--base <branch>`: Specify the base branch for cleanup (defaults to repository's `main`/`master`).
+- `--stale <days>`: Clean branches with no commits for specified days (disabled by default).
+- `--remote`: Also clean remote merged/stale branches.
+- `--dry-run`: **Default behavior**. Only list branches to be deleted without executing any operations.
+- `--yes`: Skip individual confirmations and delete all identified branches directly (suitable for CI/CD).
+- `--force`: Use `-D` to force delete local branches (even if unmerged).
+
+---
+
+## What This Command Does
+
+1. **Configuration and Safety Checks**
+   - **Update Information**: Automatically executes `git fetch --all --prune` to ensure branch status is current.
+   - **Read Protected Branches**: Reads the list of branches that should not be cleaned from Git config (see "Configuration" below).
+   - **Determine Base**: Uses `--base` parameter or auto-detected `main`/`master` as comparison baseline.
+
+2. **Analysis and Identification (Find)**
+   - **Merged Branches**: Find local (and remote if `--remote` is added) branches fully merged to `--base`.
+   - **Stale Branches**: If `--stale <days>` is specified, find branches with last commit N days ago.
+   - **Exclude Protected Branches**: Remove all configured protected branches from cleanup list.
+
+3. **Report and Preview (Report)**
+   - Clearly list "merged branches to be deleted" and "stale branches to be deleted".
+   - Without `--yes` parameter, **command ends here**, waiting for user confirmation to re-execute (without `--dry-run`).
+
+4. **Execute Cleanup (Execute)**
+   - **Only executed without `--dry-run` and after user confirmation** (or with `--yes`).
+   - Delete identified branches one by one, unless user chooses to skip in interactive confirmation.
+   - Local: `git branch -d <branch>`; Remote: `git push origin --delete <branch>`.
+   - If `--force` is specified, local deletion uses `git branch -D <branch>`.
+
+---
+
+## Configuration (Configure Once, Use Forever)
+
+To prevent accidental deletion of important branches (e.g., `develop`, `release/*`), add protection rules to the repository's Git config. The command reads them automatically.
+
+```bash
+# Protect develop branch
+git config --add branch.cleanup.protected develop
+
+# Protect all branches starting with release/ (wildcard)
+git config --add branch.cleanup.protected 'release/*'
+
+# View all configured protected branches
+git config --get-all branch.cleanup.protected
+```
+
+---
+
+## Best Practices for Embedded Devs
+
+- **Prioritize `--dry-run`**: Develop the habit of previewing before executing.
+- **Leverage `--base`**: When maintaining long-term `release` branches, use it to clean `feature` or `hotfix` branches merged to that release.
+- **Careful with `--force`**: Don't force delete unless you're 100% certain an unmerged branch is useless.
+- **Team Collaboration**: Notify the team channel before cleaning shared remote branches.
+- **Regular Runs**: Run monthly or quarterly to keep the repository clean.
+
+---
+
+## Why This Version Is Better
+
+- ✅ **Safer**: Default read-only preview with configurable protected branch list.
+- ✅ **More Flexible**: Supports custom base branches, perfectly fits `release` / `develop` workflows.
+- ✅ **More Compatible**: Avoids commands with inconsistent behavior across systems like `date -d`.
+- ✅ **More Intuitive**: Condenses complex 16-step checklist into a single command with safety options.
+- ✅ **Consistent Style**: Shares similar parameter design and documentation structure with `/commit` command.

package/templates/en/workflow/git/commands/git-commit.md

@@ -0,0 +1,152 @@
+---
+description: Analyze changes with Git only and auto-generate conventional commit messages with optional emoji; suggests splitting commits when needed, runs local Git hooks by default (use --no-verify to skip)
+allowed-tools: Read(**), Exec(git status, git diff, git add, git restore --staged, git commit, git rev-parse, git config), Write(.git/COMMIT_EDITMSG)
+argument-hint: [--no-verify] [--all] [--amend] [--signoff] [--emoji] [--scope <scope>] [--type <type>]
+# examples:
+#   - /git-commit                           # Analyze current changes, generate commit message
+#   - /git-commit --all                     # Stage all changes and commit
+#   - /git-commit --no-verify               # Skip Git hooks
+#   - /git-commit --emoji                   # Include emoji in commit message
+#   - /git-commit --scope ui --type feat    # Specify scope and type
+#   - /git-commit --amend --signoff         # Amend last commit with signature
+---
+
+# Claude Command: Commit (Git-only)
+
+This command works **without any package manager/build tools**, using only **Git** to:
+- Read changes (staged/unstaged)
+- Determine if changes should be **split into multiple commits**
+- Generate **Conventional Commits** style messages with optional emoji for each commit
+- Execute `git add` and `git commit` as needed (runs local Git hooks by default; use `--no-verify` to skip)
+
+---
+
+## Usage
+
+```bash
+/git-commit
+/git-commit --no-verify
+/git-commit --emoji
+/git-commit --all --signoff
+/git-commit --amend
+/git-commit --scope ui --type feat --emoji
+```
+
+### Options
+- `--no-verify`: Skip local Git hooks (`pre-commit`/`commit-msg` etc.).
+- `--all`: When staging area is empty, automatically `git add -A` to include all changes in the commit.
+- `--amend`: **Amend** the last commit without creating a new one (preserves author and timestamp unless local Git config specifies otherwise).
+- `--signoff`: Add `Signed-off-by` line (use when following DCO process).
+- `--emoji`: Include emoji prefix in commit message (omit for plain text).
+- `--scope <scope>`: Specify commit scope (e.g., `ui`, `docs`, `api`), written to message header.
+- `--type <type>`: Force commit type (e.g., `feat`, `fix`, `docs`), overrides automatic detection.
+
+> Note: If the framework doesn't support interactive confirmation, enable `confirm: true` in front-matter to avoid mistakes.
+
+---
+
+## What This Command Does
+
+1. **Repository/Branch Validation**
+   - Check if in a Git repository using `git rev-parse --is-inside-work-tree`.
+   - Read current branch/HEAD status; if in rebase/merge conflict state, prompt to resolve conflicts first.
+
+2. **Change Detection**
+   - Get staged and unstaged changes using `git status --porcelain` and `git diff`.
+   - If staged files = 0:
+     - If `--all` is passed → Execute `git add -A`.
+     - Otherwise prompt choice: continue analyzing unstaged changes for **suggestions**, or cancel to manually group staging.
+
+3. **Split Suggestions (Split Heuristics)**
+   - Cluster by **concerns**, **file modes**, **change types** (e.g., source code vs docs/tests; different directories/packages; additions vs deletions).
+   - If **multiple independent changesets** or large diff detected (e.g., > 300 lines / across multiple top-level directories), suggest splitting commits with pathspecs for each group (for subsequent `git add <paths>`).
+
+4. **Commit Message Generation (Conventional with Optional Emoji)**
+   - Auto-infer `type` (`feat`/`fix`/`docs`/`refactor`/`test`/`chore`/`perf`/`style`/`ci`/`revert`...) and optional `scope`.
+   - Generate message header: `[<emoji>] <type>(<scope>)?: <subject>` (first line ≤ 72 chars, imperative mood, emoji included only with `--emoji` flag).
+   - Generate message body: bullet points (motivation, implementation details, impact scope, BREAKING CHANGE if any).
+   - Write draft to `.git/COMMIT_EDITMSG` for use with `git commit`.
+
+5. **Execute Commit**
+   - Single commit scenario: `git commit [-S] [--no-verify] [-s] -F .git/COMMIT_EDITMSG`
+   - Multiple commit scenario (if split accepted): Provide clear instructions for `git add <paths> && git commit ...` per group; execute sequentially if allowed.
+
+6. **Safe Rollback**
+   - If mistakenly staged, use `git restore --staged <paths>` to unstage (command provides instructions, doesn't modify file contents).
+
+---
+
+## Best Practices for Commits
+
+- **Atomic commits**: One commit does one thing, easier to trace and review.
+- **Group before committing**: Split by directory/module/feature.
+- **Clear subject**: First line ≤ 72 chars, imperative mood (e.g., "add... / fix...").
+- **Body with context**: Explain motivation, solution, impact scope, risks, and next steps.
+- **Follow Conventional Commits**: `<type>(<scope>): <subject>`.
+
+---
+
+## Type to Emoji Mapping (When --emoji is Used)
+
+- ✨ `feat`: New feature  
+- 🐛 `fix`: Bug fix (includes 🔥 remove code/files, 🚑️ hotfix, 👽️ adapt to external API changes, 🔒️ security fix, 🚨 fix warnings, 💚 fix CI)  
+- 📝 `docs`: Documentation and comments  
+- 🎨 `style`: Code style/formatting (no semantic changes)  
+- ♻️ `refactor`: Refactoring (no new features, no bug fixes)  
+- ⚡️ `perf`: Performance improvements  
+- ✅ `test`: Add/fix tests, snapshots  
+- 🔧 `chore`: Build/tools/misc tasks (merge branches, update configs, release tags, pin dependencies, .gitignore, etc.)  
+- 👷 `ci`: CI/CD configuration and scripts  
+- ⏪️ `revert`: Revert commits  
+- 💥 `feat`: Breaking changes (explained in `BREAKING CHANGE:` section)
+
+> If `--type`/`--scope` is passed, it will **override** auto-detection.
+> Emoji is only included when `--emoji` flag is specified.
+
+---
+
+## Guidelines for Splitting Commits
+
+1. **Different concerns**: Unrelated feature/module changes should be split.  
+2. **Different types**: Don't mix `feat`, `fix`, `refactor` in the same commit.  
+3. **File modes**: Source code vs docs/tests/configs should be grouped separately.  
+4. **Size threshold**: Large diffs (e.g., >300 lines or across multiple top-level directories) should be split.  
+5. **Revertability**: Ensure each commit can be independently reverted.
+
+---
+
+## Examples
+
+**Good (with --emoji)**
+- ✨ feat(ui): add user authentication flow  
+- 🐛 fix(api): handle token refresh race condition  
+- 📝 docs: update API usage examples  
+- ♻️ refactor(core): extract retry logic into helper  
+- ✅ test: add unit tests for rate limiter  
+- 🔧 chore: update git hooks and repository settings  
+- ⏪️ revert: revert "feat(core): introduce streaming API"
+
+**Good (without --emoji)**
+- feat(ui): add user authentication flow  
+- fix(api): handle token refresh race condition  
+- docs: update API usage examples  
+- refactor(core): extract retry logic into helper  
+- test: add unit tests for rate limiter  
+- chore: update git hooks and repository settings  
+- revert: revert "feat(core): introduce streaming API"
+
+**Split Example**
+- `feat(types): add new type defs for payment method`
+- `docs: update API docs for new types`
+- `test: add unit tests for payment types`
+- `fix: address linter warnings in new files` ← (if your repo has hook errors)
+
+---
+
+## Important Notes
+
+- **Git only**: No package manager/build commands (`pnpm`/`npm`/`yarn` etc.).  
+- **Respects hooks**: Executes local Git hooks by default; use `--no-verify` to skip.  
+- **No source code changes**: Command only reads/writes `.git/COMMIT_EDITMSG` and staging area; doesn't directly edit working directory files.  
+- **Safety prompts**: In rebase/merge conflicts, detached HEAD states, prompts to handle/confirm before continuing.  
+- **Auditable and controllable**: If `confirm: true` is enabled, each actual `git add`/`git commit` step requires confirmation.

package/templates/en/workflow/git/commands/git-rollback.md

@@ -0,0 +1,89 @@
+---
+description: Interactively rollback Git branch to historical version; lists branches, versions, then executes reset/revert after confirmation
+allowed-tools: Read(**), Exec(git fetch, git branch, git tag, git log, git reflog, git checkout, git reset, git revert, git switch), Write()
+argument-hint: [--branch <branch>] [--target <rev>] [--mode reset|revert] [--depth <n>] [--dry-run] [--yes]
+# examples:
+#   - /git-rollback                # Full interactive mode, dry-run
+#   - /git-rollback --branch dev   # Select dev directly, other interactive
+#   - /git-rollback --branch dev --target v1.2.0 --mode reset --yes
+---
+# Claude Command: Git Rollback
+
+**Purpose**: Safely and visually rollback a specified branch to an older version.  
+Defaults to **read-only preview (`--dry-run`)**; actual execution requires `--yes` or interactive confirmation.
+
+---
+
+## Usage
+
+```bash
+# Pure interactive: list branches → select branch → list recent 20 versions → select target → choose reset or revert → confirm
+/git-rollback
+
+# Specify branch, other interactive
+/git-rollback --branch feature/calculator
+
+# Specify branch and target commit, execute with hard-reset in one go (dangerous)
+/git-rollback --branch main --target 1a2b3c4d --mode reset --yes
+
+# Generate revert commit only (non-destructive rollback), preview
+/git-rollback --branch release/v2.1 --target v2.0.5 --mode revert --dry-run
+```
+
+### Options
+
+| Option | Description |
+|------|------|
+| `--branch <branch>` | Branch to rollback; interactively selected if omitted. |
+| `--target <rev>` | Target version (commit hash, tag, or reflog reference); interactively selects recent `--depth` entries if omitted. |
+| `--mode reset\|revert` | `reset`: Hard rollback history; `revert`: Generate reverse commits keeping history intact. Prompts by default. |
+| `--depth <n>` | List recent n versions in interactive mode (default 20). |
+| `--dry-run` | **Enabled by default**, only preview commands to be executed. |
+| `--yes` | Skip all confirmations and execute directly, suitable for CI/CD scripts. |
+
+---
+
+## Interactive Flow
+
+1. **Sync remote** → `git fetch --all --prune`
+2. **List branches** → `git branch -a` (local + remote, filter protected branches)
+3. **Select branch** → User input or parameter
+4. **List versions** → `git log --oneline -n <depth>` + `git tag --merged` + `git reflog -n <depth>`
+5. **Select target** → User inputs commit hash / tag
+6. **Select mode** → `reset` or `revert`
+7. **Final confirmation** (unless `--yes`)
+8. **Execute rollback**  
+   * `reset`: `git switch <branch> && git reset --hard <target>`  
+   * `revert`: `git switch <branch> && git revert --no-edit <target>..HEAD`
+9. **Push suggestion** → Prompt whether to `git push --force-with-lease` (reset) or regular `git push` (revert)
+
+---
+
+## Safety Guards
+
+* **Backup**: Automatically records current HEAD in reflog before execution, recoverable with `git switch -c backup/<timestamp>`.  
+* **Protected branches**: If protected branches like `main` / `master` / `production` are detected with `reset` mode enabled, requires additional confirmation.  
+* **--dry-run enabled by default**: Prevents accidental operations.  
+* **--force prohibited**: No `--force` provided; if force push needed, manually enter `git push --force-with-lease`.
+
+---
+
+## Use Case Examples
+
+| Scenario | Command Example |
+|------|---------|
+| Hotfix patch deployed with bug, need to rollback to tag `v1.2.0` | `/git-rollback --branch release/v1 --target v1.2.0 --mode reset` |
+| Ops colleague pushed debug logs by mistake, need to generate reverse commit | `/git-rollback --branch main --target 3f2e7c9 --mode revert` |
+| Research historical bugs, guide newcomers through branch history | `/git-rollback` (full interactive, dry-run) |
+
+---
+
+## Notes
+
+1. **reset vs revert**  
+   * **reset** changes history, requires force push and may affect other collaborators, use with caution.  
+   * **revert** is safer, generates new commits preserving history, but adds one more record.  
+2. **Embedded repositories** often have large binary files; ensure LFS/submodule state consistency before rollback.  
+3. If repository has CI forced validation, rollback may trigger pipelines automatically; confirm control policies to avoid accidental deployment of old versions.
+
+---

package/templates/zh-CN/workflow/git/commands/git-cleanBranches.md

@@ -0,0 +1,101 @@
+---
+description: 安全查找并清理已合并或过期的 Git 分支，支持 dry-run 模式与自定义基准/保护分支
+allowed-tools: Read(**), Exec(git fetch, git config, git branch, git remote, git push, git for-each-ref, git log), Write()
+argument-hint: [--base <branch>] [--stale <days>] [--remote] [--force] [--dry-run] [--yes]
+# examples:
+#   - /git-cleanBranches --dry-run
+#   - /git-cleanBranches --base release/v2.1 --stale 90
+#   - /git-cleanBranches --remote --yes
+---
+
+# Claude Command: Clean Branches
+
+该命令**安全地**识别并清理**已合并**或**长期未更新 (stale)** 的 Git 分支。
+默认以**只读预览 (`--dry-run`)** 模式运行，需明确指令才会执行删除操作。
+
+---
+
+## Usage
+
+```bash
+# [最安全] 预览将要清理的分支，不执行任何删除
+/git-cleanBranches --dry-run
+
+# 清理已合并到 main 且超过 90 天未动的本地分支 (需逐一确认)
+/git-cleanBranches --stale 90
+
+# 清理已合并到 release/v2.1 的本地与远程分支 (自动确认)
+/git-cleanBranches --base release/v2.1 --remote --yes
+
+# [危险] 强制删除一个未合并的本地分支
+/git-cleanBranches --force outdated-feature
+```
+
+### Options
+- `--base <branch>`：指定清理的基准分支（默认为仓库的 `main`/`master`）。
+- `--stale <days>`：清理超过指定天数未提交的分支（默认不启用）。
+- `--remote`：同时清理远程已合并/过期的分支。
+- `--dry-run`：**默认行为**。仅列出将要删除的分支，不执行任何操作。
+- `--yes`：跳过逐一确认的步骤，直接删除所有已识别的分支（适合 CI/CD）。
+- `--force`：使用 `-D` 强制删除本地分支（即使未合并）。
+
+---
+
+## What This Command Does
+
+1. **配置与安全预检**
+   - **更新信息**：自动执行 `git fetch --all --prune`，确保分支状态最新。
+   - **读取保护分支**：从 Git 配置读取不应被清理的分支列表（见下文“Configuration”）。
+   - **确定基准**：使用 `--base` 参数或自动识别的 `main`/`master` 作为比较基准。
+
+2. **分析识别（Find）**
+   - **已合并分支**：找出已完全合并到 `--base` 的本地（及远程，如加 `--remote`）分支。
+   - **过期分支**：如指定 `--stale <days>`，找出最后一次提交在 N 天前的分支。
+   - **排除保护分支**：从待清理列表中移除所有已配置的保护分支。
+
+3. **报告预览（Report）**
+   - 清晰列出“将要删除的已合并分支”与“将要删除的过期分支”。
+   - 若无 `--yes` 参数，**命令到此结束**，等待用户确认后再次执行（不带 `--dry-run`）。
+
+4. **执行清理（Execute）**
+   - **仅在不带 `--dry-run` 且用户确认后**（或带 `--yes`）执行。
+   - 逐一删除已识别的分支，除非用户在交互式确认中选择跳过。
+   - 本地用 `git branch -d <branch>`；远程用 `git push origin --delete <branch>`。
+   - 若指定 `--force`，本地删除会改用 `git branch -D <branch>`。
+
+---
+
+## Configuration (一次配置，永久生效)
+
+为防止误删重要分支（如 `develop`, `release/*`），请在仓库的 Git 配置中添加保护规则。命令会自动读取。
+
+```bash
+# 保护 develop 分支
+git config --add branch.cleanup.protected develop
+
+# 保护所有 release/ 开头的分支 (通配符)
+git config --add branch.cleanup.protected 'release/*'
+
+# 查看所有已配置的保护分支
+git config --get-all branch.cleanup.protected
+```
+
+---
+
+## Best Practices for Embedded Devs
+
+- **优先 `--dry-run`**：养成先预览再执行的习惯。
+- **活用 `--base`**：维护长期 `release` 分支时，用它来清理已合并到该 release 的 `feature` 或 `hotfix` 分支。
+- **谨慎 `--force`**：除非你百分百确定某个未合并分支是无用功，否则不要强制删除。
+- **团队协作**：在清理共享的远程分支前，先在团队频道通知一声。
+- **定期运行**：每月或每季度运行一次，保持仓库清爽。
+
+---
+
+## Why This Version Is Better
+
+- ✅ **更安全**：默认只读预览，且有可配置的保护分支列表。
+- ✅ **更灵活**：支持自定义基准分支，完美适配 `release` / `develop` 工作流。
+- ✅ **更兼容**：避免了在不同系统上行为不一的 `date -d` 等命令。
+- ✅ **更直观**：将复杂的 16 步清单，浓缩成一个带安全选项的、可直接执行的命令。
+- ✅ **风格一致**：与 `/commit` 命令共享相似的参数设计与文档结构。

package/templates/zh-CN/workflow/git/commands/git-commit.md

@@ -0,0 +1,152 @@
+---
+description: 仅用 Git 分析改动并自动生成 conventional commit 信息（可选 emoji）；必要时建议拆分提交，默认运行本地 Git 钩子（可 --no-verify 跳过）
+allowed-tools: Read(**), Exec(git status, git diff, git add, git restore --staged, git commit, git rev-parse, git config), Write(.git/COMMIT_EDITMSG)
+argument-hint: [--no-verify] [--all] [--amend] [--signoff] [--emoji] [--scope <scope>] [--type <type>]
+# examples:
+#   - /git-commit                           # 分析当前改动，生成提交信息
+#   - /git-commit --all                     # 暂存所有改动并提交
+#   - /git-commit --no-verify               # 跳过 Git 钩子检查
+#   - /git-commit --emoji                   # 在提交信息中包含 emoji
+#   - /git-commit --scope ui --type feat    # 指定作用域和类型
+#   - /git-commit --amend --signoff         # 修补上次提交并签名
+---
+
+# Claude Command: Commit (Git‑only)
+
+该命令在**不依赖任何包管理器/构建工具**的前提下，仅通过 **Git**：
+- 读取改动（staged/unstaged）
+- 判断是否需要**拆分为多次提交**
+- 为每个提交生成 **Conventional Commits** 风格的信息（可选 emoji）
+- 按需执行 `git add` 与 `git commit`（默认运行本地 Git 钩子；可 `--no-verify` 跳过）
+
+---
+
+## Usage
+
+```bash
+/git-commit
+/git-commit --no-verify
+/git-commit --emoji
+/git-commit --all --signoff
+/git-commit --amend
+/git-commit --scope ui --type feat --emoji
+```
+
+### Options
+- `--no-verify`：跳过本地 Git 钩子（`pre-commit`/`commit-msg` 等）。
+- `--all`：当暂存区为空时，自动 `git add -A` 将所有改动纳入本次提交。
+- `--amend`：在不创建新提交的情况下**修补**上一次提交（保持提交作者与时间，除非本地 Git 配置另有指定）。
+- `--signoff`：附加 `Signed-off-by` 行（遵循 DCO 流程时使用）。
+- `--emoji`：在提交信息中包含 emoji 前缀（省略则使用纯文本）。
+- `--scope <scope>`：指定提交作用域（如 `ui`、`docs`、`api`），写入消息头部。
+- `--type <type>`：强制提交类型（如 `feat`、`fix`、`docs` 等），覆盖自动判断。
+
+> 注：如框架不支持交互式确认，可在 front‑matter 中开启 `confirm: true` 以避免误操作。
+
+---
+
+## What This Command Does
+
+1. **仓库/分支校验**
+   - 通过 `git rev-parse --is-inside-work-tree` 判断是否位于 Git 仓库。
+   - 读取当前分支/HEAD 状态；如处于 rebase/merge 冲突状态，先提示处理冲突后再继续。
+
+2. **改动检测**
+   - 用 `git status --porcelain` 与 `git diff` 获取已暂存与未暂存的改动。
+   - 若已暂存文件为 0：
+     - 若传入 `--all` → 执行 `git add -A`。
+     - 否则提示你选择：继续仅分析未暂存改动并给出**建议**，或取消命令后手动分组暂存。
+
+3. **拆分建议（Split Heuristics）**
+   - 按**关注点**、**文件模式**、**改动类型**聚类（示例：源代码 vs 文档、测试；不同目录/包；新增 vs 删除）。
+   - 若检测到**多组独立变更**或 diff 规模过大（如 > 300 行 / 跨多个顶级目录），建议拆分提交，并给出每一组的 pathspec（便于后续执行 `git add <paths>`）。
+
+4. **提交信息生成（Conventional 规范，可选 Emoji）**
+   - 自动推断 `type`（`feat`/`fix`/`docs`/`refactor`/`test`/`chore`/`perf`/`style`/`ci`/`revert` …）与可选 `scope`。
+   - 生成消息头：`[<emoji>] <type>(<scope>)?: <subject>`（首行 ≤ 72 字符，祈使语气，仅在使用 `--emoji` 时包含 emoji）。
+   - 生成消息体：要点列表（动机、实现要点、影响范围、BREAKING CHANGE 如有）。
+   - 将草稿写入 `.git/COMMIT_EDITMSG`，并用于 `git commit`。
+
+5. **执行提交**
+   - 单提交场景：`git commit [-S] [--no-verify] [-s] -F .git/COMMIT_EDITMSG`
+   - 多提交场景（如接受拆分建议）：按分组给出 `git add <paths> && git commit ...` 的明确指令；若允许执行则逐一完成。
+
+6. **安全回滚**
+   - 如误暂存，可用 `git restore --staged <paths>` 撤回暂存（命令会给出指令，不修改文件内容）。
+
+---
+
+## Best Practices for Commits
+
+- **Atomic commits**：一次提交只做一件事，便于回溯与审阅。
+- **先分组再提交**：按目录/模块/功能点拆分。
+- **清晰主题**：首行 ≤ 72 字符，祈使语气（如 “add… / fix…”）。
+- **正文含上下文**：说明动机、方案、影响范围、风险与后续工作。
+- **遵循 Conventional Commits**：`<type>(<scope>): <subject>`。
+
+---
+
+## Type 与 Emoji 映射（使用 --emoji 时）
+
+- ✨ `feat`：新增功能  
+- 🐛 `fix`：缺陷修复（含 🔥 删除代码/文件、🚑️ 紧急修复、👽️ 适配外部 API 变更、🔒️ 安全修复、🚨 解决告警、💚 修复 CI）  
+- 📝 `docs`：文档与注释  
+- 🎨 `style`：风格/格式（不改语义）  
+- ♻️ `refactor`：重构（不新增功能、不修缺陷）  
+- ⚡️ `perf`：性能优化  
+- ✅ `test`：新增/修复测试、快照  
+- 🔧 `chore`：构建/工具/杂务（合并分支、更新配置、发布标记、依赖 pin、.gitignore 等）  
+- 👷 `ci`：CI/CD 配置与脚本  
+- ⏪️ `revert`：回滚提交  
+- 💥 `feat`：破坏性变更（`BREAKING CHANGE:` 段落中说明）
+
+> 若传入 `--type`/`--scope`，将**覆盖**自动推断。
+> 仅在指定 `--emoji` 标志时才会包含 emoji。
+
+---
+
+## Guidelines for Splitting Commits
+
+1. **不同关注点**：互不相关的功能/模块改动应拆分。  
+2. **不同类型**：不要将 `feat`、`fix`、`refactor` 混在同一提交。  
+3. **文件模式**：源代码 vs 文档/测试/配置分组提交。  
+4. **规模阈值**：超大 diff（示例：>300 行或跨多个顶级目录）建议拆分。  
+5. **可回滚性**：确保每个提交可独立回退。
+
+---
+
+## Examples
+
+**Good (使用 --emoji)**
+- ✨ feat(ui): add user authentication flow  
+- 🐛 fix(api): handle token refresh race condition  
+- 📝 docs: update API usage examples  
+- ♻️ refactor(core): extract retry logic into helper  
+- ✅ test: add unit tests for rate limiter  
+- 🔧 chore: update git hooks and repository settings  
+- ⏪️ revert: revert "feat(core): introduce streaming API"
+
+**Good (不使用 --emoji)**
+- feat(ui): add user authentication flow  
+- fix(api): handle token refresh race condition  
+- docs: update API usage examples  
+- refactor(core): extract retry logic into helper  
+- test: add unit tests for rate limiter  
+- chore: update git hooks and repository settings  
+- revert: revert "feat(core): introduce streaming API"
+
+**Split Example**
+- `feat(types): add new type defs for payment method`
+- `docs: update API docs for new types`
+- `test: add unit tests for payment types`
+- `fix: address linter warnings in new files`  ←（如你的仓库有钩子报错）
+
+---
+
+## Important Notes
+
+- **仅使用 Git**：不调用任何包管理器/构建命令（无 `pnpm`/`npm`/`yarn` 等）。  
+- **尊重钩子**：默认执行本地 Git 钩子；使用 `--no-verify` 可跳过。  
+- **不改源码内容**：命令只读写 `.git/COMMIT_EDITMSG` 与暂存区；不会直接编辑工作区文件。  
+- **安全提示**：在 rebase/merge 冲突、detached HEAD 等状态下会先提示处理/确认再继续。  
+- **可审可控**：如开启 `confirm: true`，每个实际 `git add`/`git commit` 步骤都会进行二次确认。

package/templates/zh-CN/workflow/git/commands/git-rollback.md

@@ -0,0 +1,90 @@
+---
+description: 交互式回滚 Git 分支到历史版本；列分支、列版本、二次确认后执行 reset / revert
+allowed-tools: Read(**), Exec(git fetch, git branch, git tag, git log, git reflog, git checkout, git reset, git revert, git switch), Write()
+argument-hint: [--branch <branch>] [--target <rev>] [--mode reset|revert] [--depth <n>] [--dry-run] [--yes]
+# examples:
+#   - /git-rollback                # 全交互模式，dry‑run
+#   - /git-rollback --branch dev   # 直接选 dev，其他交互
+#   - /git-rollback --branch dev --target v1.2.0 --mode reset --yes
+---
+
+# Claude Command: Git Rollback
+
+**目的**：安全、可视地将指定分支回滚到旧版本。  
+默认处于 **只读预览 (`--dry-run`)**；真正执行需加 `--yes` 或在交互中确认。
+
+---
+
+## Usage
+
+```bash
+# 纯交互：列出分支 → 选分支 → 列最近 20 个版本 → 选目标 → 选择 reset 或 revert → 二次确认
+/git-rollback
+
+# 指定分支，其他交互
+/git-rollback --branch feature/calculator
+
+# 指定分支与目标 commit，并用 hard‑reset 一键执行（危险）
+/git-rollback --branch main --target 1a2b3c4d --mode reset --yes
+
+# 只想生成 revert 提交（非破坏式回滚），预览即可
+/git-rollback --branch release/v2.1 --target v2.0.5 --mode revert --dry-run
+```
+
+### Options
+
+| 选项                   | 说明                                                                               |
+| ---------------------- | ---------------------------------------------------------------------------------- |
+| `--branch <branch>`    | 要回滚的分支；缺省时交互选择。                                                     |
+| `--target <rev>`       | 目标版本（commit Hash、Tag、reflog 引用都行）；缺省时交互选择近 `--depth` 条记录。 |
+| `--mode reset\|revert` | `reset`：硬回滚历史；`revert`：生成反向提交保持历史完整。默认询问。                |
+| `--depth <n>`          | 在交互模式下列出最近 n 个版本（默认 20）。                                         |
+| `--dry-run`            | **默认开启**，只预览即将执行的命令。                                               |
+| `--yes`                | 跳过所有确认直接执行，适合 CI/CD 脚本。                                            |
+
+---
+
+## 交互流程
+
+1. **同步远端** → `git fetch --all --prune`
+2. **列分支** → `git branch -a`（本地＋远端，过滤受保护分支）
+3. **选分支** → 用户输入或传参
+4. **列版本** → `git log --oneline -n <depth>` + `git tag --merged` + `git reflog -n <depth>`
+5. **选目标** → 用户输入 commit hash / tag
+6. **选模式** → `reset` 或 `revert`
+7. **最终确认** （除非 `--yes`）
+8. **执行回滚**
+   - `reset`：`git switch <branch> && git reset --hard <target>`
+   - `revert`：`git switch <branch> && git revert --no-edit <target>..HEAD`
+9. **推送建议** → 提示是否 `git push --force-with-lease`（reset）或普通 `git push`（revert）
+
+---
+
+## 安全护栏
+
+- **备份**：执行前自动在 reflog 中记录当前 HEAD，可用 `git switch -c backup/<timestamp>` 恢复。
+- **保护分支**：如检测到 `main` / `master` / `production` 等受保护分支且开启 `reset` 模式，将要求额外确认。
+- **--dry-run 默认开启**：防止误操作。
+- **--force 禁止**：不提供 `--force`；如需强推，请手动输入 `git push --force-with-lease`。
+
+---
+
+## 适用场景示例
+
+| 场景                                            | 调用示例                                                         |
+| ----------------------------------------------- | ---------------------------------------------------------------- |
+| 热修补丁上线后发现 bug，需要回到 Tag `v1.2.0`   | `/git-rollback --branch release/v1 --target v1.2.0 --mode reset` |
+| 运维同事误推了 debug 日志提交，需要生成反向提交 | `/git-rollback --branch main --target 3f2e7c9 --mode revert`     |
+| 调研历史 bug，引导新人浏览分支历史              | `/git-rollback` （全交互，dry‑run）                              |
+
+---
+
+## 注意
+
+1. **reset vs revert**
+   - **reset** 会改变历史，需要强推并可能影响其他协作者，谨慎使用。
+   - **revert** 更安全，生成新提交保留历史，但会增加一次记录。
+2. **嵌入式仓库** 常有大体积二进制文件；回滚前请确保 LFS/子模块状态一致。
+3. 若仓库启用了 CI 强制校验，回滚后可能自动触发流水线；确认管控策略以免误部署旧版本。
+
+---