@moon791017/neo-skills 1.1.15 → 1.1.18

package/README.md

@@ -85,48 +85,18 @@ node bin/install-skills.js
 
 ### Agent Skills CLI 安裝
 
-Agent Skills CLI 會從 GitHub repository 探索 `skills/` 與 `.agents/skills/`。請明確指定目標 Agent，避免使用 `--all` 時同時選取不支援全域安裝的 Agent。
-
-| Agent | `--agent` ID |
-| :--- | :--- |
-| Claude Code | `claude-code` |
-| Copilot CLI | `github-copilot` |
-| Codex | `codex` |
-| Antigravity CLI | `antigravity-cli` |
-
-安裝全部技能到目前專案（以 Codex 為例）：
-
-```bash
-npx skills add Benknightdark/neo-skills --skill '*' --agent codex -y
-```
-
-安裝全部技能到全域（以 Codex 為例）：
-
-```bash
-npx skills add Benknightdark/neo-skills --skill '*' --agent codex -g -y
-```
-
-同時安裝到多個 Agent 時，重複傳入 `--agent`：
+安裝全部技能到目前專案：
 
 ```bash
-npx skills add Benknightdark/neo-skills --skill '*' \
-  --agent codex \
-  --agent antigravity-cli \
-  -g -y
+npx skills add Benknightdark/neo-skills --skill --all -y
 ```
 
-只安裝指定技能時，重複傳入 `--skill`：
+安裝全部技能到全域：
 
 ```bash
-npx skills add Benknightdark/neo-skills \
-  --skill neo-typescript \
-  --skill neo-vue \
-  --agent codex \
-  -y
+npx skills add Benknightdark/neo-skills --skill --all -g -y
 ```
 
-> `--all` 等同同時選取全部技能與全部 Agent。不要使用 `--all -g` 表示「全域安裝全部技能」；Eve 與 PromptScript 僅支援專案範圍，會使該組合回報安裝失敗。
-
 ## 系統提示詞安裝
 
 Agent Skills 規格同步的是技能目錄；`AGENTS.md`、`CLAUDE.md`、Copilot instructions 或 Antigravity `agents.md` 這類指導檔需要另外安裝。

package/package.json

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

package/skills/neo-pr/SKILL.md

@@ -79,29 +79,23 @@ Construct the PR Title and Description based on extracted commit and diff contex
 
 #### 1. PR Title Standard (Conventional Commits)
 * Format: `<type>(<scope>): <short summary>`
-* Example: `feat(auth): add JWT authorization and automatic token refresh`
+* Example: `feat(auth): 新增 JWT 驗證與 Token 自動刷新`
 * Rules:
   - Do not begin with filler phrases ("This PR implements...", "A commit to...").
   - Keep under 50 characters, imperative mood, direct and actionable.
 
-#### 2. PR Description Standard (Bulleted Structure)
-The PR body must contain the following four sections, formatted strictly with **bullet points**:
+#### 2. PR Output Standard Structure
+The PR output **must strictly be wrapped in a Markdown code block** (i.e. raw Markdown source code ` ```markdown ... ``` `) so that users can easily copy it directly into GitHub/GitLab PR description fields. The content inside the code block must consist exclusively of the following two sections:
 
+````markdown
 ```markdown
-## 📌 Motivation
-- Explain why this change is required, the bug it resolves, or feature requirement it fulfills.
+標題：
+<Conventional Commits 格式標題>
 
-## 🛠️ Key Changes
-- Highlight primary modification points (list critical module/file updates and structural logic shifts).
-- Avoid line-by-line code repetition; focus on high-level architecture and logic evolution.
-
-## ⚠️ Impact & Breaking Changes
-- Note any breaking changes, API contract updates, or database schema migrations.
-- Write `None` if there is no significant impact.
-
-## 🧪 Verification & Test Steps
-- List passed unit tests or manual verification steps (including exact execution commands).
+內容：
+- 列點並重點化的說明重要變更內容（包含主要模組/檔案調整、邏輯變更與重大影響）。
 ```
+````
 
 #### 3. Strict De-slop Rules
 * ❌ Never use: "It is worth noting that", "Needless to say", "This PR aims to", "In summary", "Clearly".

package/skills/neo-pr/evals/evals.json

@@ -4,10 +4,11 @@
     {
       "id": 1,
       "prompt": "Generate a concise, non-AI-slop PR title and description for merging feature/user-auth into main.",
-      "expected_output": "A PR title adhering to Conventional Commits format, and a bulleted markdown PR description covering Motivation, Key Changes, Impact & Breaking Changes, and Verification & Test Steps with no AI fluff phrases.",
+      "expected_output": "A PR title adhering to Conventional Commits format under '標題：', and a bulleted markdown PR description under '內容：' wrapped in a Markdown code block for easy copying, with no AI fluff phrases.",
       "assertions": [
-        "PR Title complies with Conventional Commits format",
-        "PR Description includes Motivation, Key Changes, Impact & Breaking Changes, and Verification sections",
+        "PR output is enclosed inside a Markdown code block for easy copying",
+        "PR Title complies with Conventional Commits format under 標題：",
+        "PR Description includes bullet points summarizing key changes under 內容：",
         "Content is structured strictly with bullet points",
         "Does not contain AI tells like 'It is worth noting that' or 'This PR aims to'"
       ]

package/skills/neo-pr/references/pr-template.md

@@ -19,33 +19,22 @@ Titles must be clear, concise, and directly reflect the underlying changes using
 * `chore`: Changes to the build process, auxiliary tools, or dependencies
 * `perf`: A code change that improves performance
 
-### Title Examples:
-- ✅ `feat(auth): add Google OAuth login flow and token handler`
-- ✅ `fix(cart): resolve overflow in checkout discount calculation`
-- ✅ `refactor(db): extract user repository to domain service layer`
-- ❌ `Updated some code` (Too vague)
-- ❌ `feat(auth): this PR dramatically improves auth security and UX` (Contains AI fluff)
-
 ---
 
 ## 2. PR Description Template
 
-```markdown
-## 📌 Motivation
-- [Briefly describe the issue solved, context, or feature request fulfilled]
-
-## 🛠️ Key Changes
-- [Key point 1: Modified module/file and rationale]
-- [Key point 2: Added logic or architectural improvement]
-- [Key point 3: Environment or dependency adjustments]
+The PR output **must strictly be wrapped in a Markdown code block** (i.e. raw Markdown source code ` ```markdown ... ``` `) so that users can easily copy it directly into GitHub/GitLab PR description fields. The output format must strictly follow:
 
-## ⚠️ Impact & Breaking Changes
-- [Detail impacts on other modules, API contracts, or DB schemas. State "None" if inapplicable]
+````markdown
+```markdown
+標題：
+<type>(<scope>): <short summary>
 
-## 🧪 Verification & Test Steps
-- [List automated tests executed, e.g., `npm test` or `dotnet test`]
-- [Manual verification steps and expected outcomes]
+內容：
+- **[重要變更/關鍵模組 1]**：說明具體調整內容與目的。
+- **[重要變更/關鍵模組 2]**：說明具體調整內容與目的。
 ```
+````
 
 ---
 
@@ -55,7 +44,6 @@ When drafting PR descriptions, rigorously filter out filler words according to t
 
 | ❌ Fluff Phrase | ⭕ Clean Alternative | Explanation |
 | :--- | :--- | :--- |
-| It is worth noting that this PR refactors auth logic. | Refactor authorization logic to use unified middleware. | Delete throat-clearing openers; use direct action verbs. |
-| This PR aims to resolve a potential crash during login. | Fix crash during login caused by null User reference. | Omit "This PR aims to"; state goal and root cause directly. |
-| In summary, this change seamlessly boosts system performance. | Reduce DB queries, lowering API latency by 40ms. | Replace "seamlessly" with concrete metrics. |
-| Imagine a scenario where unhandled requests hit the server... | Add defensive 401 error handling for unauthenticated requests. | Remove hypothetical setups; state defensive logic clearly. |
+| It is worth noting that this PR refactors auth logic. | 重構驗證邏輯，改用統一中介軟體。 | Delete throat-clearing openers; use direct action verbs. |
+| This PR aims to resolve a potential crash during login. | 修復登入時因 null 使用者引發的閃退問題。 | Omit "This PR aims to"; state goal and root cause directly. |
+| In summary, this change seamlessly boosts system performance. | 減少 DB 查詢，降低 API 延遲 40ms。 | Replace "seamlessly" with concrete metrics. |