@moon791017/neo-skills 1.0.35 → 1.0.36

package/GEMINI.md

@@ -82,8 +82,6 @@ When interacting with this codebase or using the extension, the agent follows th
 
 *   **Web Scraper:** 從指定的 URL 獲取網頁 HTML 內容，支援 CSS 選擇器 (`fetch_web_content`)。
 
-*   **Git Automation:** 根據暫存區變更自動生成 Conventional Commits 訊息，經使用者確認後執行 commit。
-
 *   **CI Protocols:** 自動配置 .NET 專案的 Azure Pipelines CI 建置流程。
 
 *   **CD Protocols:** 為專案自動配置 Azure App Service 與地端 IIS 的部署流程 (CD)。

package/README.md

@@ -27,10 +27,7 @@
     *   **Azure App Service**：部署至Azure App Service。
     *   **IIS On-Premises**：部署至地端 IIS 伺服器，包含備份與復原機制。
 
-### 2. 智慧 Git 助手
-*   **Smart Commit**：根據 `git diff` 暫存區內容，自動生成符合 Conventional Commits 規範的提交訊息。
-
-### 3. Code Review 專家
+### 2. Code Review 專家
 *   **智能審查**：針對程式碼變更進行多面向 (正確性、安全性、效能、可讀性) 的深度審查。
 
 ### 4. 程式碼解釋助手
@@ -185,6 +182,7 @@ install-system-instructions --instructions <key> [--ai-agent <name>] [--project-
 | Key | 名稱 | 說明 |
 | :--- | :--- | :--- |
 | `technical-co-founder` | Technical Co-Founder | 讓 AI 扮演技術共同創辦人，以 Discovery → Planning → Building → Polish → Handoff 五階段框架，協助您從零打造可上線的真實產品。 |
+| `git-commit` | Git Commit Message Generator | 分析暫存區變更，自動生成符合 Conventional Commits 規範的提交訊息，經確認後執行。 |
 
 **範例：**
 

package/bin/_system-instructions.js

@@ -46,6 +46,34 @@ Rules:
 • This is real. Not a mockup. Not a prototype. A working product.
 • Keep me in control and in the loop at all times`;
 
+export const gitCommitInstructions = `
+## Git Commit Guidelines
+
+All commit messages must strictly adopt Conventional Commits 1.0.0 (CC 1.0.0).
+
+- Format: \`<type>[optional scope][!]: <description>\`.
+- \`type\` must be a lowercase noun; prioritize using \`feat\`, \`fix\`, \`docs\`, \`test\`, \`refactor\`, \`build\`, \`ci\`, \`chore\`.
+- \`feat\` indicates a new feature, corresponding to SemVer minor; \`fix\` indicates a bug fix, corresponding to SemVer patch.
+- \`scope\` is optional, use a lowercase short noun, e.g., \`docs\`, \`scanner\`, \`npm\`, \`ci\`.
+- \`description\` is required, write in the imperative mood, present tense, in English, and do not end with a period.
+- Major breaking changes must have a \`!\` added after the type/scope, or use \`BREAKING CHANGE: <description>\` in the footer; this kind of commit corresponds to SemVer major.
+- Body is optional, must be separated from the header by a blank line, used to explain motivation, background, and behavioral differences, without restating the diff.
+- Footer is optional, must be separated from the body by a blank line; issue references use \`Refs: #123\` or \`Closes: #123\`.
+- Multi-line commit messages must use actual newline characters to separate header, body, and footer; do not write the literal string \`\\n\` into the commit message or git log.
+- Each commit focuses on a single logical change; do not mix unrelated modifications in the same commit.
+- Before committing, ensure you do not include unrequested or existing unrelated changes.
+
+Examples:
+
+\`\`\`text
+docs(readme): add localized documentation links
+
+feat(scanner)!: change default risk threshold
+
+BREAKING CHANGE: scans now fail CI when findings are at or above the threshold
+\`\`\`
+`;
+
 /**
  * 系統提示詞 Registry — 以 kebab-case 作為 key，供 CLI 選擇安裝。
  *
@@ -58,4 +86,8 @@ export const INSTRUCTIONS = {
     name: 'Technical Co-Founder',
     content: technicalCoFounderInstructions,
   },
+  'git-commit': {
+    name: 'Git Commit Message Generator',
+    content: gitCommitInstructions,
+  },
 };

package/gemini-extension.json

@@ -1,7 +1,7 @@
 {
   "name": "neo-skills",
   "description": "A universal capability extension for Gemini CLI",
-  "version": "0.59.0",
+  "version": "0.60.0",
   "mcpServers": {
     "neo-skills": {
       "command": "node",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@moon791017/neo-skills",
-  "version": "1.0.35",
+  "version": "1.0.36",
   "type": "module",
   "description": "Neo Skills: A Universal Expert Agent Extension",
   "homepage": "https://neo-blog-iota.vercel.app/",

package/skills/neo-git-commit/SKILL.md

@@ -1,88 +0,0 @@
----
-name: neo-git-commit
-description: Analyzes staged changes, generates a high-quality Conventional Commits message in Traditional Chinese, and executes the commit only after user confirmation.
-disable-model-invocation: true
----
-
-# Git Commit Message Generator
-
-## CRITICAL SAFETY PROTOCOL
-
-- **Absolute prohibition**: Never execute `git commit` in the same turn you generate the commit message.
-- **Wait for confirmation**: Output the proposed message, then stop immediately and ask the user to confirm.
-- **User-triggered only**: Only execute the commit in the next turn if the user explicitly replies with "yes", "ok", "是", or "commit".
-- **No commit trailers**: Do **not** generate or append any commit trailer lines such as `Co-authored-by:`, `Signed-off-by:`, `Reviewed-by:`, or similar metadata unless the user explicitly requests them.
-
----
-
-## Perceive
-
-1. Run `git add .` to stage all changes.
-2. Run `git diff --staged` to retrieve the full staged diff.
-3. If the staging area is empty, inform the user "No staged changes found." and stop.
-
-## Reason
-
-Analyze the diff to determine the core intent of the changes:
-
-1. **Full scan**: Identify added, deleted, and modified files.
-2. **Find correlations**: Determine whether the changes serve a single goal (e.g., adding a Model and updating a Service indicates a feature implementation).
-3. **Filter noise**: Ignore pure formatting adjustments (whitespace, line endings) and focus on logical changes.
-4. **Define type**: Choose the most accurate Conventional Commits type based on the primary purpose of the changes.
-
-## Act
-
-### Step 1: Generate the commit message
-
-Output strictly in the following format:
-
-```
-<type>(<scope>): <subject>
-
-<body>
-```
-
-**Type** — choose the most appropriate one:
-
-| Type | When to use |
-|------|-------------|
-| `feat` | New feature |
-| `fix` | Bug fix |
-| `docs` | Documentation changes only |
-| `style` | Formatting, no logic change |
-| `refactor` | Refactoring, not a feature or fix |
-| `perf` | Performance improvement |
-| `test` | Adding or modifying tests |
-| `build` | Build system or dependency changes |
-| `ci` | CI/CD configuration changes |
-| `chore` | Other maintenance tasks |
-| `revert` | Reverting a previous commit |
-
-**Quality rules**:
-
-- **Subject**: Max 50 characters, imperative mood (e.g., "新增...", "修復...", "移除...").
-- **Body**:
-  - Use bullet points (`-`) for complex changes to explain each detail.
-  - May be omitted for simple documentation or minor fixes.
-  - For new files, describe their purpose.
-- **Language**: Both Subject and Body must be written in **Traditional Chinese (Taiwan)**.
-- **Tone**: Professional and concise — avoid filler phrases like "This change is for...".
-- **Forbidden content**: Do **not** include `Co-authored-by`, `Signed-off-by`, or any other trailer/footer metadata in the generated commit message.
-
-### Step 2: Ask for confirmation
-
-Output the generated commit message inside a code block, then **stop immediately** and ask:
-
-> 請問是否要執行此 commit？（輸入「是」或「yes」確認）
-
-### Step 3: Execute (only after user confirms)
-
-Run:
-
-```bash
-git commit -m "<subject>" -m "<body>"
-```
-
-Do not append any extra trailer/footer metadata unless the user explicitly requests it.
-
-After execution, run `git log --oneline -1` and display the result to confirm the commit was created successfully.