plugins/git
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix(pr): 行為清單那三支腳本的路徑也補上外掛目錄名

Browse Source 
上一筆只改了技能本文，行為清單漏掉。新的路徑檢核腳本一跑就指出來——關鍵
步驟與外部呼叫兩欄還留著八處不帶前綴的寫法，而那兩欄正是別人拿來確認這支
技能會呼叫誰的地方。

順手改掉技能本文開頭那一句的舉例方式。原本把不帶前綴的錯誤寫法原樣寫出來
當例子，那一行自己就會被路徑檢核當成一處待改。改成描述後果、不照抄那個
寫法，順便講得更準：省掉外掛目錄名之後，路徑會相對於當下的工作目錄解，
可能解到自己這個存取庫裡對的那一支、可能解到別的 domain 底下另一支，也可能
什麼都解不到。中間那一種最糟，它會跑起來，跑的是另一支腳本。

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
jiantw83
2026-09-04 10:51:31 +08:00
co-authored by Claude Opus 5
parent 5d3f761677
commit 003593c73a
2 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
skills/pr/SKILL.md
+1 -1
View File
@@ -7,7 +7,7 @@ description: Commit all changes via jsc-git:commit, name a ladder-shaped target
The ladder rules live in one place only: section 「PR 分支階梯」 of `jsc-meta/references/guidelines.md`. `jsc-git/tools/base-branch.sh --derive` is the running implementation of that section. Read the rung a branch belongs to there; never hand-pick a base, and never restate the ladder table in this file.
Every script path in this file starts with its plugin's own directory name — `jsc-git/tools/…` for this plugin's, `jsc-gitea/tools/…` and `jsc-hooks/tools/…` for the others — and is resolved against the tool root the caller supplies, never against this skill's own directory. These three scripts sit at the plugin root, not under `skills/pr/`, so a bare `tools/base-branch.sh` resolves to a path that does not exist and exits 127. That failure is worse than it looks: step 4 says never hand-pick a base, and an agent that cannot run the deriver is one step away from picking one anyway, which turns a wrong path into a PR opened against the wrong rung.
Every script path in this file starts with its plugin's own directory name — `jsc-git/tools/…` for this plugin's, `jsc-gitea/tools/…` and `jsc-hooks/tools/…` for the others — and is resolved against the tool root the caller supplies, never against this skill's own directory. These three scripts sit at the plugin root, not under `skills/pr/`, so dropping the plugin directory name leaves a path that resolves against whatever the current directory happens to be — the right script inside this repo, a different domain's script outside it, or nothing at all and exit 127. That failure is worse than it looks: step 4 says never hand-pick a base, and an agent that cannot run the deriver is one step away from picking one anyway, which turns a wrong path into a PR opened against the wrong rung.
## Steps