pipwave-ekyc-uikit 3.2.1-beta.1 → 3.2.2-beta.1
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.
|
@@ -0,0 +1,47 @@
|
|
|
1
|
+
---
|
|
2
|
+
description: Write a release message for the current branch's changes in our house style
|
|
3
|
+
argument-hint: <Fix|Enhancement|New> [target-branch] [--short]
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
Write a release message for the changes on the CURRENT branch, which are merging
|
|
7
|
+
into a target branch. Do not repeat prompting overhead back to me — just produce
|
|
8
|
+
the message.
|
|
9
|
+
|
|
10
|
+
## Inputs (from "$ARGUMENTS")
|
|
11
|
+
- **Type** (required): one of `Fix`, `Enhancement`, `New` (case-insensitive; also accept `Fixes`).
|
|
12
|
+
- **Target branch** (optional): the branch these changes merge INTO. Default `origin/master`.
|
|
13
|
+
- **`--short`** (optional flag): also/instead produce a tighter one-liner.
|
|
14
|
+
|
|
15
|
+
If the type is missing or ambiguous, ask me once; otherwise proceed without questions.
|
|
16
|
+
|
|
17
|
+
## Steps
|
|
18
|
+
1. Resolve the target branch (default `origin/master`). Run:
|
|
19
|
+
- `git log <target>..HEAD --oneline --no-merges`
|
|
20
|
+
- `git diff <target>...HEAD --stat`
|
|
21
|
+
- `git diff <target>...HEAD -- <the changed source files>` (skip `dist/`, lockfiles, version-only bumps)
|
|
22
|
+
2. Read the actual source diff to understand the real user/merchant-facing impact — do not
|
|
23
|
+
paraphrase the commit subject; describe what changed and why it matters to the user.
|
|
24
|
+
3. Pull the Shortcut ID (`sc-XXXXXX`) from the branch name or commit subjects.
|
|
25
|
+
4. Output ONE sentence (may use commas/clauses), prefixed with `[sc-XXXXXX]`.
|
|
26
|
+
|
|
27
|
+
## House style by type
|
|
28
|
+
|
|
29
|
+
**Fix** — state the symptom that was broken, then the fix.
|
|
30
|
+
Open with "Fixed" or "Fixes".
|
|
31
|
+
> [sc-338198] Fixed selfie auto-capturing off-center or too-close faces by adding real-time centering and distance guards that block capture until the face is properly framed.
|
|
32
|
+
|
|
33
|
+
**Enhancement** — improves existing behavior. Open with an action verb ("Changed",
|
|
34
|
+
"Increased", "Skipped") or "<feature> now ...".
|
|
35
|
+
> [sc-326139] Increased camera capture area size to enhance resolution of submitted document images.
|
|
36
|
+
|
|
37
|
+
**New** — a brand-new capability. Open with "Introduced", "Added", or "Implemented".
|
|
38
|
+
> [sc-334995] Real-time card edge detection that automatically captures the document the moment its edges are properly aligned within the frame, with live on-screen feedback so users no longer have to tap the capture button themselves.
|
|
39
|
+
|
|
40
|
+
## Tone rules
|
|
41
|
+
- User/merchant-facing outcome first, mechanism second. Not a changelog of files touched.
|
|
42
|
+
- One sentence. Concrete (name the feature/page/behavior), not abstract.
|
|
43
|
+
- No em dash "—"; use a colon or comma.
|
|
44
|
+
- No bold, headers, emoji, or bullet lists in the message itself.
|
|
45
|
+
- If `--short`, also give a tighter variant that keeps the `[sc-XXXXXX]` prefix and the core outcome.
|
|
46
|
+
|
|
47
|
+
After the message, offer light follow-ups (shorter version, different type framing) rather than over-producing.
|
|
@@ -1,10 +1,11 @@
|
|
|
1
1
|
{
|
|
2
2
|
"permissions": {
|
|
3
3
|
"allow": [
|
|
4
|
-
"Bash(
|
|
5
|
-
"
|
|
6
|
-
"
|
|
7
|
-
"Bash(
|
|
4
|
+
"Bash(xargs git log --oneline -1)",
|
|
5
|
+
"Skill(code-review)",
|
|
6
|
+
"Skill(code-review:*)",
|
|
7
|
+
"Bash(kill 60053 69150 84076)",
|
|
8
|
+
"Bash(lsof -iTCP -sTCP:LISTEN -P -n)"
|
|
8
9
|
]
|
|
9
10
|
}
|
|
10
11
|
}
|