@moon791017/neo-skills 1.1.17 → 1.1.18
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json
CHANGED
package/skills/neo-pr/SKILL.md
CHANGED
|
@@ -85,8 +85,9 @@ Construct the PR Title and Description based on extracted commit and diff contex
|
|
|
85
85
|
- Keep under 50 characters, imperative mood, direct and actionable.
|
|
86
86
|
|
|
87
87
|
#### 2. PR Output Standard Structure
|
|
88
|
-
The PR output must strictly consist of
|
|
88
|
+
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:
|
|
89
89
|
|
|
90
|
+
````markdown
|
|
90
91
|
```markdown
|
|
91
92
|
標題：
|
|
92
93
|
<Conventional Commits 格式標題>
|
|
@@ -94,6 +95,7 @@ The PR output must strictly consist of only the following two sections:
|
|
|
94
95
|
內容：
|
|
95
96
|
- 列點並重點化的說明重要變更內容（包含主要模組/檔案調整、邏輯變更與重大影響）。
|
|
96
97
|
```
|
|
98
|
+
````
|
|
97
99
|
|
|
98
100
|
#### 3. Strict De-slop Rules
|
|
99
101
|
* ❌ Never use: "It is worth noting that", "Needless to say", "This PR aims to", "In summary", "Clearly".
|
|
@@ -4,8 +4,9 @@
|
|
|
4
4
|
{
|
|
5
5
|
"id": 1,
|
|
6
6
|
"prompt": "Generate a concise, non-AI-slop PR title and description for merging feature/user-auth into main.",
|
|
7
|
-
"expected_output": "A PR title adhering to Conventional Commits format under '標題：', and a bulleted markdown PR description under '內容：' with no AI fluff phrases.",
|
|
7
|
+
"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.",
|
|
8
8
|
"assertions": [
|
|
9
|
+
"PR output is enclosed inside a Markdown code block for easy copying",
|
|
9
10
|
"PR Title complies with Conventional Commits format under 標題：",
|
|
10
11
|
"PR Description includes bullet points summarizing key changes under 內容：",
|
|
11
12
|
"Content is structured strictly with bullet points",
|
|
@@ -23,8 +23,9 @@ Titles must be clear, concise, and directly reflect the underlying changes using
|
|
|
23
23
|
|
|
24
24
|
## 2. PR Description Template
|
|
25
25
|
|
|
26
|
-
The PR output format must strictly follow:
|
|
26
|
+
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:
|
|
27
27
|
|
|
28
|
+
````markdown
|
|
28
29
|
```markdown
|
|
29
30
|
標題：
|
|
30
31
|
<type>(<scope>): <short summary>
|
|
@@ -33,6 +34,7 @@ The PR output format must strictly follow:
|
|
|
33
34
|
- **[重要變更/關鍵模組 1]**：說明具體調整內容與目的。
|
|
34
35
|
- **[重要變更/關鍵模組 2]**：說明具體調整內容與目的。
|
|
35
36
|
```
|
|
37
|
+
````
|
|
36
38
|
|
|
37
39
|
---
|
|
38
40
|
|