kiokuko 1.0.5 → 1.0.6
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/README.ja.md +27 -0
- package/README.ko.md +27 -0
- package/README.md +32 -0
- package/README.zh-CN.md +27 -0
- package/dist/setup/standard-skills.d.ts +7 -0
- package/dist/setup/standard-skills.d.ts.map +1 -1
- package/dist/setup/standard-skills.js +13 -0
- package/dist/setup/standard-skills.js.map +1 -1
- package/docs/README.ja.md +1 -0
- package/docs/README.md +1 -0
- package/package.json +4 -2
- package/skills/kiokuko-soul/SKILL.md +12 -3
- package/skills/one-shot-software-completion/SKILL.md +54 -0
- package/skills/one-shot-software-completion/references/boundaries-and-lifecycle.md +56 -0
- package/skills/one-shot-software-completion/references/discovery-and-scope.md +67 -0
- package/skills/one-shot-software-completion/references/failure-recovery.md +43 -0
- package/skills/one-shot-software-completion/references/verification-and-completion.md +62 -0
package/README.ja.md
CHANGED
|
@@ -41,6 +41,33 @@ kiokuko setup --no-embeddings
|
|
|
41
41
|
|
|
42
42
|
埋め込みのセットアップを省略します。既存の埋め込み設定は変更しません。
|
|
43
43
|
|
|
44
|
+
<a id="setup-messages"></a>
|
|
45
|
+
|
|
46
|
+
### npmの通知とセットアップエラー
|
|
47
|
+
|
|
48
|
+
`install scripts not yet covered by allowScripts`は、依存パッケージのスクリプトに実行許可が記録されていないという通知です。
|
|
49
|
+
`esbuild`はビルドツール、`fsevents`はmacOSのファイル監視用です。この通知だけではセットアップの失敗とは限りません。
|
|
50
|
+
|
|
51
|
+
通知が出たパッケージのディレクトリで確認します。
|
|
52
|
+
|
|
53
|
+
```bash
|
|
54
|
+
npm install-scripts ls
|
|
55
|
+
```
|
|
56
|
+
|
|
57
|
+
`esbuild`と`fsevents`が表示され、スクリプトを確認したうえで実行を許可する場合は、次のコマンドで記録します。
|
|
58
|
+
|
|
59
|
+
```bash
|
|
60
|
+
npm install-scripts approve esbuild fsevents
|
|
61
|
+
```
|
|
62
|
+
|
|
63
|
+
許可はそのディレクトリの`package.json`に保存されます。macOSでKiokukoをグローバルインストールした場合は、エラーに表示されたKiokukoのインストール先で実行してください。
|
|
64
|
+
別のプロジェクトで実行すると、そのプロジェクトの許可設定を確認・変更します。
|
|
65
|
+
詳しくは[npmのスクリプト許可ガイド](https://docs.npmjs.com/cli/v11/commands/npm-install-scripts/)を参照してください。
|
|
66
|
+
|
|
67
|
+
最後に`Local semantic retrieval dependencies remain unavailable`と`Cannot find package ... @huggingface/hub/index.js`が出た場合は、
|
|
68
|
+
埋め込みランタイムを読み込めず、semantic検索の設定が完了していません。スクリプトの許可でこの読み込みエラーが直るとは確認できていません。
|
|
69
|
+
問い合わせる際は、エラー全文と`kiokuko --version`、`node --version`、`npm --version`の結果を添えてください。
|
|
70
|
+
|
|
44
71
|
## アンインストール
|
|
45
72
|
|
|
46
73
|
Kiokukoを使うクライアントと`kiokuko serve`を終了してから実行します。
|
package/README.ko.md
CHANGED
|
@@ -38,6 +38,33 @@ kiokuko setup --no-embeddings
|
|
|
38
38
|
|
|
39
39
|
임베딩 설정 단계를 건너뛰며 기존 임베딩 설정은 변경하지 않습니다.
|
|
40
40
|
|
|
41
|
+
<a id="setup-messages"></a>
|
|
42
|
+
|
|
43
|
+
### npm 알림과 설정 오류
|
|
44
|
+
|
|
45
|
+
`install scripts not yet covered by allowScripts`는 해당 의존성 스크립트의 실행 승인이 npm에 기록되지 않았다는 뜻입니다.
|
|
46
|
+
`esbuild`는 빌드 도구이고, `fsevents`는 macOS 파일 감시에 사용됩니다. 이 알림만으로 설정이 실패했다고 볼 수는 없습니다.
|
|
47
|
+
|
|
48
|
+
알림이 발생한 패키지 디렉터리에서 확인하세요.
|
|
49
|
+
|
|
50
|
+
```bash
|
|
51
|
+
npm install-scripts ls
|
|
52
|
+
```
|
|
53
|
+
|
|
54
|
+
`esbuild`와 `fsevents`가 표시되고, 스크립트를 검토한 뒤 실행을 허용하려면 다음 명령으로 승인을 기록하세요.
|
|
55
|
+
|
|
56
|
+
```bash
|
|
57
|
+
npm install-scripts approve esbuild fsevents
|
|
58
|
+
```
|
|
59
|
+
|
|
60
|
+
승인은 해당 디렉터리의 `package.json`에 저장됩니다. macOS에 Kiokuko를 전역 설치했다면 오류에 표시된 Kiokuko 설치 디렉터리에서 실행하세요.
|
|
61
|
+
다른 프로젝트에서 실행하면 그 프로젝트의 승인 설정을 조회하고 변경합니다.
|
|
62
|
+
자세한 내용은 [npm 스크립트 승인 안내](https://docs.npmjs.com/cli/v11/commands/npm-install-scripts/)를 참조하세요.
|
|
63
|
+
|
|
64
|
+
설정이 `Local semantic retrieval dependencies remain unavailable`과 `Cannot find package ... @huggingface/hub/index.js`로 끝나면,
|
|
65
|
+
임베딩 런타임을 불러오지 못해 semantic 검색 설정이 완료되지 않은 상태입니다. 스크립트 승인으로 이 불러오기 오류가 해결되는지는 확인되지 않았습니다.
|
|
66
|
+
도움을 요청할 때는 전체 오류와 `kiokuko --version`, `node --version`, `npm --version`의 출력을 첨부하세요.
|
|
67
|
+
|
|
41
68
|
## 제거
|
|
42
69
|
|
|
43
70
|
Kiokuko를 사용하는 클라이언트와 `kiokuko serve`를 먼저 종료하세요.
|
package/README.md
CHANGED
|
@@ -44,6 +44,38 @@ kiokuko setup --no-embeddings
|
|
|
44
44
|
|
|
45
45
|
This skips embedding setup and preserves any existing embedding settings.
|
|
46
46
|
|
|
47
|
+
<a id="setup-messages"></a>
|
|
48
|
+
|
|
49
|
+
### npm notices and setup errors
|
|
50
|
+
|
|
51
|
+
`install scripts not yet covered by allowScripts` means npm has no recorded
|
|
52
|
+
approval for those dependency scripts. `esbuild` is a build tool; `fsevents`
|
|
53
|
+
supports macOS file watching. The notice alone does not mean setup failed.
|
|
54
|
+
|
|
55
|
+
Run this in the package directory that produced the notice:
|
|
56
|
+
|
|
57
|
+
```bash
|
|
58
|
+
npm install-scripts ls
|
|
59
|
+
```
|
|
60
|
+
|
|
61
|
+
If it lists `esbuild` and `fsevents`, and you have reviewed and want to allow their
|
|
62
|
+
scripts, record approval with:
|
|
63
|
+
|
|
64
|
+
```bash
|
|
65
|
+
npm install-scripts approve esbuild fsevents
|
|
66
|
+
```
|
|
67
|
+
|
|
68
|
+
Approval updates that directory's `package.json`. For a global macOS Kiokuko
|
|
69
|
+
install, use the installed Kiokuko directory shown in the error; running these
|
|
70
|
+
commands in another project reviews and changes that project's policy.
|
|
71
|
+
See [npm's script approval guide](https://docs.npmjs.com/cli/v11/commands/npm-install-scripts/).
|
|
72
|
+
|
|
73
|
+
If setup ends with `Local semantic retrieval dependencies remain unavailable`
|
|
74
|
+
and `Cannot find package ... @huggingface/hub/index.js`, the embedding runtime
|
|
75
|
+
could not load and semantic setup is incomplete. Script approval is not a
|
|
76
|
+
confirmed fix for this import error. Report the full error and the output of
|
|
77
|
+
`kiokuko --version`, `node --version`, and `npm --version` when requesting help.
|
|
78
|
+
|
|
47
79
|
## Uninstall
|
|
48
80
|
|
|
49
81
|
Stop clients using Kiokuko and any `kiokuko serve` process first.
|
package/README.zh-CN.md
CHANGED
|
@@ -38,6 +38,33 @@ kiokuko setup --no-embeddings
|
|
|
38
38
|
|
|
39
39
|
此选项跳过嵌入设置步骤,不更改已有的嵌入配置。
|
|
40
40
|
|
|
41
|
+
<a id="setup-messages"></a>
|
|
42
|
+
|
|
43
|
+
### npm 提示与设置错误
|
|
44
|
+
|
|
45
|
+
`install scripts not yet covered by allowScripts` 表示 npm 尚未记录这些依赖脚本的执行许可。
|
|
46
|
+
`esbuild` 是构建工具,`fsevents` 用于 macOS 文件监控。仅出现此提示不代表设置失败。
|
|
47
|
+
|
|
48
|
+
在产生提示的包目录中运行:
|
|
49
|
+
|
|
50
|
+
```bash
|
|
51
|
+
npm install-scripts ls
|
|
52
|
+
```
|
|
53
|
+
|
|
54
|
+
如果列出了 `esbuild` 和 `fsevents`,并且你已检查脚本、决定允许执行,可运行:
|
|
55
|
+
|
|
56
|
+
```bash
|
|
57
|
+
npm install-scripts approve esbuild fsevents
|
|
58
|
+
```
|
|
59
|
+
|
|
60
|
+
许可会写入该目录的 `package.json`。在 macOS 上全局安装 Kiokuko 时,请在错误信息显示的 Kiokuko 安装目录中操作;
|
|
61
|
+
在其他项目中运行这些命令,查看和修改的是那个项目的许可设置。
|
|
62
|
+
详情请参阅 [npm 脚本许可指南](https://docs.npmjs.com/cli/v11/commands/npm-install-scripts/)。
|
|
63
|
+
|
|
64
|
+
如果设置最终报出 `Local semantic retrieval dependencies remain unavailable` 和 `Cannot find package ... @huggingface/hub/index.js`,
|
|
65
|
+
说明嵌入运行时无法加载,semantic 检索尚未配置完成。尚未确认批准脚本能解决此导入错误。
|
|
66
|
+
寻求帮助时,请附上完整错误信息以及 `kiokuko --version`、`node --version`、`npm --version` 的输出。
|
|
67
|
+
|
|
41
68
|
## 卸载
|
|
42
69
|
|
|
43
70
|
先退出使用 Kiokuko 的客户端和 `kiokuko serve`。
|
|
@@ -23,6 +23,9 @@ export declare const STANDARD_WORKFLOW_SKILL_FILES: readonly ["SKILL.md"];
|
|
|
23
23
|
export declare const STANDARD_JAPANESE_SKILL_NAME = "natural-japanese-output";
|
|
24
24
|
export declare const STANDARD_JAPANESE_SKILL_MANAGED_MARKER = "<!-- KIOKUKO MANAGED STANDARD SKILL: natural-japanese-output -->";
|
|
25
25
|
export declare const STANDARD_JAPANESE_SKILL_FILES: readonly ["SKILL.md"];
|
|
26
|
+
export declare const STANDARD_COMPLETION_SKILL_NAME = "one-shot-software-completion";
|
|
27
|
+
export declare const STANDARD_COMPLETION_SKILL_MANAGED_MARKER = "<!-- KIOKUKO MANAGED STANDARD SKILL: one-shot-software-completion -->";
|
|
28
|
+
export declare const STANDARD_COMPLETION_SKILL_FILES: readonly ["SKILL.md", "references/discovery-and-scope.md", "references/boundaries-and-lifecycle.md", "references/verification-and-completion.md", "references/failure-recovery.md"];
|
|
26
29
|
export declare const STANDARD_SKILL_MANIFESTS: readonly [{
|
|
27
30
|
readonly name: "kiokuko-ui-design-soul";
|
|
28
31
|
readonly managedMarker: "<!-- KIOKUKO MANAGED STANDARD SKILL: kiokuko-ui-design-soul -->";
|
|
@@ -47,6 +50,10 @@ export declare const STANDARD_SKILL_MANIFESTS: readonly [{
|
|
|
47
50
|
readonly name: "natural-japanese-output";
|
|
48
51
|
readonly managedMarker: "<!-- KIOKUKO MANAGED STANDARD SKILL: natural-japanese-output -->";
|
|
49
52
|
readonly files: readonly ["SKILL.md"];
|
|
53
|
+
}, {
|
|
54
|
+
readonly name: "one-shot-software-completion";
|
|
55
|
+
readonly managedMarker: "<!-- KIOKUKO MANAGED STANDARD SKILL: one-shot-software-completion -->";
|
|
56
|
+
readonly files: readonly ["SKILL.md", "references/discovery-and-scope.md", "references/boundaries-and-lifecycle.md", "references/verification-and-completion.md", "references/failure-recovery.md"];
|
|
50
57
|
}, {
|
|
51
58
|
readonly name: "kiokuko-soul";
|
|
52
59
|
readonly managedMarker: "<!-- KIOKUKO MANAGED STANDARD SKILL: kiokuko-soul -->";
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"standard-skills.d.ts","sourceRoot":"","sources":["../../src/setup/standard-skills.ts"],"names":[],"mappings":"AAKA,eAAO,MAAM,sBAAsB,2BAA2B,CAAC;AAC/D,eAAO,MAAM,gCAAgC,oEAAoE,CAAC;AAClH,eAAO,MAAM,sBAAsB,qHAOzB,CAAC;AACX,eAAO,MAAM,wBAAwB,+OAO3B,CAAC;AACX,eAAO,MAAM,uBAAuB,yRAI1B,CAAC;AACX,eAAO,MAAM,0BAA0B,wBAAwB,CAAC;AAChE,eAAO,MAAM,oCAAoC,iEAAiE,CAAC;AACnH,eAAO,MAAM,2BAA2B,uBAAwB,CAAC;AACjE,eAAO,MAAM,4BAA4B,qCAAqC,CAAC;AAC/E,eAAO,MAAM,sCAAsC,8EAA8E,CAAC;AAClI,eAAO,MAAM,4BAA4B,oIAO/B,CAAC;AACX,eAAO,MAAM,8BAA8B,gPAOjC,CAAC;AACX,eAAO,MAAM,6BAA6B,gUAKhC,CAAC;AACX,eAAO,MAAM,0BAA0B,qBAAqB,CAAC;AAC7D,eAAO,MAAM,oCAAoC,8DAA8D,CAAC;AAChH,eAAO,MAAM,2BAA2B,uBAAwB,CAAC;AACjE,eAAO,MAAM,wBAAwB,iBAAiB,CAAC;AACvD,eAAO,MAAM,kCAAkC,0DAA0D,CAAC;AAC1G,eAAO,MAAM,yBAAyB,uBAAwB,CAAC;AAC/D,eAAO,MAAM,4BAA4B,6BAA6B,CAAC;AACvE,eAAO,MAAM,sCAAsC,sEAAsE,CAAC;AAC1H,eAAO,MAAM,6BAA6B,uBAAwB,CAAC;AACnE,eAAO,MAAM,4BAA4B,4BAA4B,CAAC;AACtE,eAAO,MAAM,sCAAsC,qEAAqE,CAAC;AACzH,eAAO,MAAM,6BAA6B,uBAAwB,CAAC;
|
|
1
|
+
{"version":3,"file":"standard-skills.d.ts","sourceRoot":"","sources":["../../src/setup/standard-skills.ts"],"names":[],"mappings":"AAKA,eAAO,MAAM,sBAAsB,2BAA2B,CAAC;AAC/D,eAAO,MAAM,gCAAgC,oEAAoE,CAAC;AAClH,eAAO,MAAM,sBAAsB,qHAOzB,CAAC;AACX,eAAO,MAAM,wBAAwB,+OAO3B,CAAC;AACX,eAAO,MAAM,uBAAuB,yRAI1B,CAAC;AACX,eAAO,MAAM,0BAA0B,wBAAwB,CAAC;AAChE,eAAO,MAAM,oCAAoC,iEAAiE,CAAC;AACnH,eAAO,MAAM,2BAA2B,uBAAwB,CAAC;AACjE,eAAO,MAAM,4BAA4B,qCAAqC,CAAC;AAC/E,eAAO,MAAM,sCAAsC,8EAA8E,CAAC;AAClI,eAAO,MAAM,4BAA4B,oIAO/B,CAAC;AACX,eAAO,MAAM,8BAA8B,gPAOjC,CAAC;AACX,eAAO,MAAM,6BAA6B,gUAKhC,CAAC;AACX,eAAO,MAAM,0BAA0B,qBAAqB,CAAC;AAC7D,eAAO,MAAM,oCAAoC,8DAA8D,CAAC;AAChH,eAAO,MAAM,2BAA2B,uBAAwB,CAAC;AACjE,eAAO,MAAM,wBAAwB,iBAAiB,CAAC;AACvD,eAAO,MAAM,kCAAkC,0DAA0D,CAAC;AAC1G,eAAO,MAAM,yBAAyB,uBAAwB,CAAC;AAC/D,eAAO,MAAM,4BAA4B,6BAA6B,CAAC;AACvE,eAAO,MAAM,sCAAsC,sEAAsE,CAAC;AAC1H,eAAO,MAAM,6BAA6B,uBAAwB,CAAC;AACnE,eAAO,MAAM,4BAA4B,4BAA4B,CAAC;AACtE,eAAO,MAAM,sCAAsC,qEAAqE,CAAC;AACzH,eAAO,MAAM,6BAA6B,uBAAwB,CAAC;AAEnE,eAAO,MAAM,8BAA8B,iCAAiC,CAAC;AAC7E,eAAO,MAAM,wCAAwC,0EAA0E,CAAC;AAChI,eAAO,MAAM,+BAA+B,qLAMlC,CAAC;AAQX,eAAO,MAAM,wBAAwB;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;EAgCiB,CAAC;AAEvD,MAAM,WAAW,wBAAwB;IACvC,QAAQ,CAAC,SAAS,EAAE,MAAM,CAAC;IAC3B,QAAQ,CAAC,aAAa,EAAE,MAAM,CAAC;IAC/B,QAAQ,CAAC,YAAY,EAAE,MAAM,CAAC;IAC9B,QAAQ,CAAC,OAAO,EAAE,MAAM,CAAC;CAC1B;AAkCD,wBAAsB,6BAA6B,IAAI,OAAO,CAAC,wBAAwB,EAAE,CAAC,CAEzF;AAED,wBAAgB,uBAAuB,CACrC,QAAQ,EAAE,MAAM,GAAG,SAAS,EAC5B,OAAO,EAAE,wBAAwB,EACjC,eAAe,CAAC,EAAE,MAAM,GACvB;IAAE,OAAO,EAAE,MAAM,CAAC;IAAC,MAAM,EAAE,SAAS,GAAG,SAAS,GAAG,WAAW,CAAA;CAAE,CAclE"}
|
|
@@ -64,6 +64,15 @@ export const STANDARD_WORKFLOW_SKILL_FILES = ['SKILL.md'];
|
|
|
64
64
|
export const STANDARD_JAPANESE_SKILL_NAME = 'natural-japanese-output';
|
|
65
65
|
export const STANDARD_JAPANESE_SKILL_MANAGED_MARKER = '<!-- KIOKUKO MANAGED STANDARD SKILL: natural-japanese-output -->';
|
|
66
66
|
export const STANDARD_JAPANESE_SKILL_FILES = ['SKILL.md'];
|
|
67
|
+
export const STANDARD_COMPLETION_SKILL_NAME = 'one-shot-software-completion';
|
|
68
|
+
export const STANDARD_COMPLETION_SKILL_MANAGED_MARKER = '<!-- KIOKUKO MANAGED STANDARD SKILL: one-shot-software-completion -->';
|
|
69
|
+
export const STANDARD_COMPLETION_SKILL_FILES = [
|
|
70
|
+
'SKILL.md',
|
|
71
|
+
'references/discovery-and-scope.md',
|
|
72
|
+
'references/boundaries-and-lifecycle.md',
|
|
73
|
+
'references/verification-and-completion.md',
|
|
74
|
+
'references/failure-recovery.md',
|
|
75
|
+
];
|
|
67
76
|
export const STANDARD_SKILL_MANIFESTS = [{
|
|
68
77
|
name: STANDARD_UI_SKILL_NAME,
|
|
69
78
|
managedMarker: STANDARD_UI_SKILL_MANAGED_MARKER,
|
|
@@ -88,6 +97,10 @@ export const STANDARD_SKILL_MANIFESTS = [{
|
|
|
88
97
|
name: STANDARD_JAPANESE_SKILL_NAME,
|
|
89
98
|
managedMarker: STANDARD_JAPANESE_SKILL_MANAGED_MARKER,
|
|
90
99
|
files: STANDARD_JAPANESE_SKILL_FILES,
|
|
100
|
+
}, {
|
|
101
|
+
name: STANDARD_COMPLETION_SKILL_NAME,
|
|
102
|
+
managedMarker: STANDARD_COMPLETION_SKILL_MANAGED_MARKER,
|
|
103
|
+
files: STANDARD_COMPLETION_SKILL_FILES,
|
|
91
104
|
}, {
|
|
92
105
|
name: STANDARD_SOUL_SKILL_NAME,
|
|
93
106
|
managedMarker: STANDARD_SOUL_SKILL_MANAGED_MARKER,
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"standard-skills.js","sourceRoot":"","sources":["../../src/setup/standard-skills.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,QAAQ,EAAE,MAAM,kBAAkB,CAAC;AAC5C,OAAO,IAAI,MAAM,WAAW,CAAC;AAC7B,OAAO,EAAE,aAAa,EAAE,MAAM,UAAU,CAAC;AACzC,OAAO,EAAE,YAAY,EAAE,MAAM,cAAc,CAAC;AAE5C,MAAM,CAAC,MAAM,sBAAsB,GAAG,wBAAwB,CAAC;AAC/D,MAAM,CAAC,MAAM,gCAAgC,GAAG,iEAAiE,CAAC;AAClH,MAAM,CAAC,MAAM,sBAAsB,GAAG;IACpC,mBAAmB;IACnB,aAAa;IACb,aAAa;IACb,qBAAqB;IACrB,cAAc;IACd,cAAc;CACN,CAAC;AACX,MAAM,CAAC,MAAM,wBAAwB,GAAG;IACtC,oCAAoC;IACpC,8BAA8B;IAC9B,kCAAkC;IAClC,4CAA4C;IAC5C,uCAAuC;IACvC,iCAAiC;CACzB,CAAC;AACX,MAAM,CAAC,MAAM,uBAAuB,GAAG;IACrC,UAAU;IACV,GAAG,wBAAwB;IAC3B,4BAA4B;CACpB,CAAC;AACX,MAAM,CAAC,MAAM,0BAA0B,GAAG,qBAAqB,CAAC;AAChE,MAAM,CAAC,MAAM,oCAAoC,GAAG,8DAA8D,CAAC;AACnH,MAAM,CAAC,MAAM,2BAA2B,GAAG,CAAC,UAAU,CAAU,CAAC;AACjE,MAAM,CAAC,MAAM,4BAA4B,GAAG,kCAAkC,CAAC;AAC/E,MAAM,CAAC,MAAM,sCAAsC,GAAG,2EAA2E,CAAC;AAClI,MAAM,CAAC,MAAM,4BAA4B,GAAG;IAC1C,kBAAkB;IAClB,gBAAgB;IAChB,iBAAiB;IACjB,kBAAkB;IAClB,sBAAsB;IACtB,kBAAkB;CACV,CAAC;AACX,MAAM,CAAC,MAAM,8BAA8B,GAAG;IAC5C,wCAAwC;IACxC,gCAAgC;IAChC,gCAAgC;IAChC,yCAAyC;IACzC,4BAA4B;IAC5B,4CAA4C;CACpC,CAAC;AACX,MAAM,CAAC,MAAM,6BAA6B,GAAG;IAC3C,UAAU;IACV,GAAG,8BAA8B;IACjC,gCAAgC;IAChC,gCAAgC;CACxB,CAAC;AACX,MAAM,CAAC,MAAM,0BAA0B,GAAG,kBAAkB,CAAC;AAC7D,MAAM,CAAC,MAAM,oCAAoC,GAAG,2DAA2D,CAAC;AAChH,MAAM,CAAC,MAAM,2BAA2B,GAAG,CAAC,UAAU,CAAU,CAAC;AACjE,MAAM,CAAC,MAAM,wBAAwB,GAAG,cAAc,CAAC;AACvD,MAAM,CAAC,MAAM,kCAAkC,GAAG,uDAAuD,CAAC;AAC1G,MAAM,CAAC,MAAM,yBAAyB,GAAG,CAAC,UAAU,CAAU,CAAC;AAC/D,MAAM,CAAC,MAAM,4BAA4B,GAAG,0BAA0B,CAAC;AACvE,MAAM,CAAC,MAAM,sCAAsC,GAAG,mEAAmE,CAAC;AAC1H,MAAM,CAAC,MAAM,6BAA6B,GAAG,CAAC,UAAU,CAAU,CAAC;AACnE,MAAM,CAAC,MAAM,4BAA4B,GAAG,yBAAyB,CAAC;AACtE,MAAM,CAAC,MAAM,sCAAsC,GAAG,kEAAkE,CAAC;AACzH,MAAM,CAAC,MAAM,6BAA6B,GAAG,CAAC,UAAU,CAAU,CAAC;
|
|
1
|
+
{"version":3,"file":"standard-skills.js","sourceRoot":"","sources":["../../src/setup/standard-skills.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,QAAQ,EAAE,MAAM,kBAAkB,CAAC;AAC5C,OAAO,IAAI,MAAM,WAAW,CAAC;AAC7B,OAAO,EAAE,aAAa,EAAE,MAAM,UAAU,CAAC;AACzC,OAAO,EAAE,YAAY,EAAE,MAAM,cAAc,CAAC;AAE5C,MAAM,CAAC,MAAM,sBAAsB,GAAG,wBAAwB,CAAC;AAC/D,MAAM,CAAC,MAAM,gCAAgC,GAAG,iEAAiE,CAAC;AAClH,MAAM,CAAC,MAAM,sBAAsB,GAAG;IACpC,mBAAmB;IACnB,aAAa;IACb,aAAa;IACb,qBAAqB;IACrB,cAAc;IACd,cAAc;CACN,CAAC;AACX,MAAM,CAAC,MAAM,wBAAwB,GAAG;IACtC,oCAAoC;IACpC,8BAA8B;IAC9B,kCAAkC;IAClC,4CAA4C;IAC5C,uCAAuC;IACvC,iCAAiC;CACzB,CAAC;AACX,MAAM,CAAC,MAAM,uBAAuB,GAAG;IACrC,UAAU;IACV,GAAG,wBAAwB;IAC3B,4BAA4B;CACpB,CAAC;AACX,MAAM,CAAC,MAAM,0BAA0B,GAAG,qBAAqB,CAAC;AAChE,MAAM,CAAC,MAAM,oCAAoC,GAAG,8DAA8D,CAAC;AACnH,MAAM,CAAC,MAAM,2BAA2B,GAAG,CAAC,UAAU,CAAU,CAAC;AACjE,MAAM,CAAC,MAAM,4BAA4B,GAAG,kCAAkC,CAAC;AAC/E,MAAM,CAAC,MAAM,sCAAsC,GAAG,2EAA2E,CAAC;AAClI,MAAM,CAAC,MAAM,4BAA4B,GAAG;IAC1C,kBAAkB;IAClB,gBAAgB;IAChB,iBAAiB;IACjB,kBAAkB;IAClB,sBAAsB;IACtB,kBAAkB;CACV,CAAC;AACX,MAAM,CAAC,MAAM,8BAA8B,GAAG;IAC5C,wCAAwC;IACxC,gCAAgC;IAChC,gCAAgC;IAChC,yCAAyC;IACzC,4BAA4B;IAC5B,4CAA4C;CACpC,CAAC;AACX,MAAM,CAAC,MAAM,6BAA6B,GAAG;IAC3C,UAAU;IACV,GAAG,8BAA8B;IACjC,gCAAgC;IAChC,gCAAgC;CACxB,CAAC;AACX,MAAM,CAAC,MAAM,0BAA0B,GAAG,kBAAkB,CAAC;AAC7D,MAAM,CAAC,MAAM,oCAAoC,GAAG,2DAA2D,CAAC;AAChH,MAAM,CAAC,MAAM,2BAA2B,GAAG,CAAC,UAAU,CAAU,CAAC;AACjE,MAAM,CAAC,MAAM,wBAAwB,GAAG,cAAc,CAAC;AACvD,MAAM,CAAC,MAAM,kCAAkC,GAAG,uDAAuD,CAAC;AAC1G,MAAM,CAAC,MAAM,yBAAyB,GAAG,CAAC,UAAU,CAAU,CAAC;AAC/D,MAAM,CAAC,MAAM,4BAA4B,GAAG,0BAA0B,CAAC;AACvE,MAAM,CAAC,MAAM,sCAAsC,GAAG,mEAAmE,CAAC;AAC1H,MAAM,CAAC,MAAM,6BAA6B,GAAG,CAAC,UAAU,CAAU,CAAC;AACnE,MAAM,CAAC,MAAM,4BAA4B,GAAG,yBAAyB,CAAC;AACtE,MAAM,CAAC,MAAM,sCAAsC,GAAG,kEAAkE,CAAC;AACzH,MAAM,CAAC,MAAM,6BAA6B,GAAG,CAAC,UAAU,CAAU,CAAC;AAEnE,MAAM,CAAC,MAAM,8BAA8B,GAAG,8BAA8B,CAAC;AAC7E,MAAM,CAAC,MAAM,wCAAwC,GAAG,uEAAuE,CAAC;AAChI,MAAM,CAAC,MAAM,+BAA+B,GAAG;IAC7C,UAAU;IACV,mCAAmC;IACnC,wCAAwC;IACxC,2CAA2C;IAC3C,gCAAgC;CACxB,CAAC;AAQX,MAAM,CAAC,MAAM,wBAAwB,GAAG,CAAC;QACvC,IAAI,EAAE,sBAAsB;QAC5B,aAAa,EAAE,gCAAgC;QAC/C,KAAK,EAAE,uBAAuB;KAC/B,EAAE;QACD,IAAI,EAAE,0BAA0B;QAChC,aAAa,EAAE,oCAAoC;QACnD,KAAK,EAAE,2BAA2B;KACnC,EAAE;QACD,IAAI,EAAE,4BAA4B;QAClC,aAAa,EAAE,sCAAsC;QACrD,KAAK,EAAE,6BAA6B;KACrC,EAAE;QACD,IAAI,EAAE,0BAA0B;QAChC,aAAa,EAAE,oCAAoC;QACnD,KAAK,EAAE,2BAA2B;KACnC,EAAE;QACD,IAAI,EAAE,4BAA4B;QAClC,aAAa,EAAE,sCAAsC;QACrD,KAAK,EAAE,6BAA6B;KACrC,EAAE;QACD,IAAI,EAAE,4BAA4B;QAClC,aAAa,EAAE,sCAAsC;QACrD,KAAK,EAAE,6BAA6B;KACrC,EAAE;QACD,IAAI,EAAE,8BAA8B;QACpC,aAAa,EAAE,wCAAwC;QACvD,KAAK,EAAE,+BAA+B;KACvC,EAAE;QACD,IAAI,EAAE,wBAAwB;QAC9B,aAAa,EAAE,kCAAkC;QACjD,KAAK,EAAE,yBAAyB;KACjC,CAAqD,CAAC;AASvD,SAAS,iBAAiB,CAAC,SAAiB;IAC1C,MAAM,eAAe,GAAG,IAAI,CAAC,OAAO,CAAC,aAAa,CAAC,MAAM,CAAC,IAAI,CAAC,GAAG,CAAC,CAAC,CAAC;IACrE,OAAO,IAAI,CAAC,OAAO,CAAC,eAAe,EAAE,IAAI,EAAE,IAAI,EAAE,QAAQ,EAAE,SAAS,CAAC,CAAC;AACxE,CAAC;AAED,SAAS,WAAW,CAAC,OAAe,EAAE,aAAqB;IACzD,OAAO,OAAO,CAAC,KAAK,CAAC,aAAa,CAAC,CAAC,MAAM,GAAG,CAAC,CAAC;AACjD,CAAC;AAED,KAAK,UAAU,wBAAwB,CACrC,QAA+B;IAE/B,MAAM,IAAI,GAAG,iBAAiB,CAAC,QAAQ,CAAC,IAAI,CAAC,CAAC;IAC9C,OAAO,OAAO,CAAC,GAAG,CAAC,QAAQ,CAAC,KAAK,CAAC,GAAG,CAAC,KAAK,EAAE,YAAY,EAAE,EAAE;QAC3D,IAAI,OAAe,CAAC;QACpB,IAAI,CAAC;YACH,OAAO,GAAG,MAAM,QAAQ,CAAC,IAAI,CAAC,IAAI,CAAC,IAAI,EAAE,YAAY,CAAC,EAAE,MAAM,CAAC,CAAC;QAClE,CAAC;QAAC,MAAM,CAAC;YACP,MAAM,IAAI,YAAY,CAAC,iBAAiB,EAAE,+CAA+C,QAAQ,CAAC,IAAI,IAAI,YAAY,EAAE,CAAC,CAAC;QAC5H,CAAC;QACD,IAAI,WAAW,CAAC,OAAO,EAAE,QAAQ,CAAC,aAAa,CAAC,KAAK,CAAC,EAAE,CAAC;YACvD,MAAM,IAAI,YAAY,CAAC,iBAAiB,EAAE,iEAAiE,QAAQ,CAAC,IAAI,IAAI,YAAY,EAAE,CAAC,CAAC;QAC9I,CAAC;QACD,OAAO;YACL,SAAS,EAAE,QAAQ,CAAC,IAAI;YACxB,aAAa,EAAE,QAAQ,CAAC,aAAa;YACrC,YAAY;YACZ,OAAO;SACR,CAAC;IACJ,CAAC,CAAC,CAAC,CAAC;AACN,CAAC;AAED,MAAM,CAAC,KAAK,UAAU,6BAA6B;IACjD,OAAO,CAAC,MAAM,OAAO,CAAC,GAAG,CAAC,wBAAwB,CAAC,GAAG,CAAC,wBAAwB,CAAC,CAAC,CAAC,CAAC,IAAI,EAAE,CAAC;AAC5F,CAAC;AAED,MAAM,UAAU,uBAAuB,CACrC,QAA4B,EAC5B,OAAiC,EACjC,eAAwB;IAExB,IAAI,QAAQ,KAAK,SAAS;QAAE,OAAO,EAAE,OAAO,EAAE,OAAO,CAAC,OAAO,EAAE,MAAM,EAAE,SAAS,EAAE,CAAC;IACnF,IAAI,WAAW,CAAC,QAAQ,EAAE,OAAO,CAAC,aAAa,CAAC,KAAK,CAAC,EAAE,CAAC;QACvD,MAAM,MAAM,GAAG,eAAe,IAAI,GAAG,OAAO,CAAC,SAAS,IAAI,OAAO,CAAC,YAAY,EAAE,CAAC;QACjF,MAAM,IAAI,YAAY,CACpB,UAAU,EACV,2DAA2D,MAAM,sEAAsE,EACvI,EAAE,IAAI,EAAE,MAAM,EAAE,CACjB,CAAC;IACJ,CAAC;IACD,OAAO;QACL,OAAO,EAAE,OAAO,CAAC,OAAO;QACxB,MAAM,EAAE,QAAQ,KAAK,OAAO,CAAC,OAAO,CAAC,CAAC,CAAC,WAAW,CAAC,CAAC,CAAC,SAAS;KAC/D,CAAC;AACJ,CAAC"}
|
package/docs/README.ja.md
CHANGED
|
@@ -3,6 +3,7 @@
|
|
|
3
3
|
目的別に参照してください。
|
|
4
4
|
|
|
5
5
|
- [導入ガイド](getting-started.ja.md) — インストール、Codex/OpenCode/Claude/Hermes設定、再起動、Web UI。
|
|
6
|
+
- [npmの通知とセットアップエラー](../README.ja.md#setup-messages) — スクリプトの許可を確認し、埋め込み依存関係のエラーと区別する。
|
|
6
7
|
- [基本概念](concepts.ja.md) — RAG、記憶のライフサイクル、Project/Ecosystem/Global、Akinator。
|
|
7
8
|
- [Semantic retrieval](semantic-retrieval.ja.md) — embedding runtime、運用、offline、fallback。
|
|
8
9
|
- [Akinator のプロフィール補助](akinator-memory.md) — 候補提示、限定的な対象補完、索引の再構築。
|
package/docs/README.md
CHANGED
|
@@ -3,6 +3,7 @@
|
|
|
3
3
|
Choose a guide by what you need to do:
|
|
4
4
|
|
|
5
5
|
- [Getting started](getting-started.md) — install, configure Codex/OpenCode/Claude/Hermes, restart clients, and use the Web UI.
|
|
6
|
+
- [npm notices and setup errors](../README.md#setup-messages) — review script approvals and distinguish them from missing embedding dependencies.
|
|
6
7
|
- [Concepts](concepts.md) — RAG, memory lifecycle, Project/Ecosystem/Global scopes, and Akinator.
|
|
7
8
|
- [Semantic retrieval](semantic-retrieval.md) — embedding runtime setup, operation, offline mode, and fallback.
|
|
8
9
|
- [Akinator profile memory](akinator-memory.md) — optional hints, strict target resolution, and index rebuilding.
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "kiokuko",
|
|
3
|
-
"version": "1.0.
|
|
3
|
+
"version": "1.0.6",
|
|
4
4
|
"description": "Model-agnostic external memory for AI coding agents",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"bin": {
|
|
@@ -58,7 +58,9 @@
|
|
|
58
58
|
"allowScripts": {
|
|
59
59
|
"onnxruntime-node": true,
|
|
60
60
|
"sharp": true,
|
|
61
|
-
"protobufjs": true
|
|
61
|
+
"protobufjs": true,
|
|
62
|
+
"esbuild@0.28.2": true,
|
|
63
|
+
"fsevents@2.3.3": true
|
|
62
64
|
},
|
|
63
65
|
"peerDependencies": {
|
|
64
66
|
"@huggingface/hub": "2.16.1",
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: kiokuko-soul
|
|
3
|
-
description: Use before every non-trivial Kiokuko-governed task as the mandatory first-read SOUL router. Run the Akinator intake gate before planning or implementation, then route simple code work, general code work, and interactive UI work to the bundled specialist Skills.
|
|
3
|
+
description: Use before every coding request, including small fixes, and every other non-trivial Kiokuko-governed task as the mandatory first-read SOUL router. Run the Akinator intake gate before planning or implementation, then route simple code work, general code work, and interactive UI work to the bundled specialist Skills.
|
|
4
4
|
---
|
|
5
5
|
|
|
6
6
|
<!-- KIOKUKO MANAGED STANDARD SKILL: kiokuko-soul -->
|
|
@@ -9,7 +9,7 @@ description: Use before every non-trivial Kiokuko-governed task as the mandatory
|
|
|
9
9
|
|
|
10
10
|
## Outcome
|
|
11
11
|
|
|
12
|
-
Start every non-trivial Kiokuko-governed task by reading one stable router, resolving the Akinator intake gate, then reading the applicable compact specialist indexes and only the expert fragments required by the current task.
|
|
12
|
+
Start every coding request (including small fixes) and every other non-trivial Kiokuko-governed task by reading one stable router, resolving the Akinator intake gate, then reading the applicable compact specialist indexes and only the expert fragments required by the current task.
|
|
13
13
|
|
|
14
14
|
This Skill owns the entry sequence and routes work. Akinator is the mandatory intake state machine, not a specialist route. This Skill does not duplicate specialist instructions, select another model, or authorize effects beyond the user request and current client permissions.
|
|
15
15
|
|
|
@@ -72,6 +72,14 @@ This route minimizes the solution; it does not replace the code contract below o
|
|
|
72
72
|
|
|
73
73
|
Read and apply the `kiokuko-single-purpose-functions` index before writing, modifying, debugging, refactoring, or reviewing code, and before decomposing a code-changing plan. Select one to three `code.*` expert fragments for each cohesive function or task.
|
|
74
74
|
|
|
75
|
+
### Software completion for every coding request
|
|
76
|
+
|
|
77
|
+
Before code-changing planning or implementation, apply the compact
|
|
78
|
+
`one-shot-software-completion/SKILL.md` core, including for small, minimal/YAGNI,
|
|
79
|
+
test and UI changes. Reuse its unchanged full text already in active context;
|
|
80
|
+
otherwise read it. A summary is insufficient. Load references only for concrete
|
|
81
|
+
risks; this route does not require reading them all. Follow availability rules below.
|
|
82
|
+
|
|
75
83
|
### Interactive UI work
|
|
76
84
|
|
|
77
85
|
Read and apply the `kiokuko-ui-design-soul` index before designing, implementing, modifying, debugging, or reviewing an interactive interface. Select one to three `ui.*` expert fragments for the actual interaction risks. If UI work changes code, apply both the code and UI indexes.
|
|
@@ -87,7 +95,8 @@ Use this order:
|
|
|
87
95
|
3. `veteran-programmer-skill` when the change crosses workflow stages;
|
|
88
96
|
4. `kiokuko-simple-work` when the finalized intake satisfies the simple-code activation boundary;
|
|
89
97
|
5. `kiokuko-single-purpose-functions` for code planning or code work;
|
|
90
|
-
6. `
|
|
98
|
+
6. `one-shot-software-completion` for every coding request, including simple code and UI code changes;
|
|
99
|
+
7. `kiokuko-ui-design-soul` for interactive UI work.
|
|
91
100
|
|
|
92
101
|
Keep each route within the user-approved task scope.
|
|
93
102
|
|
|
@@ -0,0 +1,54 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: one-shot-software-completion
|
|
3
|
+
description: Required before planning or implementing any code change, including small fixes, tests and UI. Read this compact core; load references only for concrete risks.
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
<!-- KIOKUKO MANAGED STANDARD SKILL: one-shot-software-completion -->
|
|
7
|
+
|
|
8
|
+
<!-- kiokuko:runtime contract -->
|
|
9
|
+
# One-Shot Software Completion
|
|
10
|
+
|
|
11
|
+
Deliver the user's observable result, not an isolated patch. One-shot is a
|
|
12
|
+
delivery goal, not a promise of success in one turn or extra authorization.
|
|
13
|
+
|
|
14
|
+
## Activation and context
|
|
15
|
+
|
|
16
|
+
For every coding request, including minimal/YAGNI work, apply this entire core
|
|
17
|
+
before code-changing planning or implementation. Follow `kiokuko-soul` and host
|
|
18
|
+
intake, scope and permissions; this Skill grants no extra agents or continuation.
|
|
19
|
+
Reuse the unchanged full core already in active context, including host-supplied
|
|
20
|
+
text. Read it when absent, changed or lost to compaction; a summary or capability
|
|
21
|
+
listing is insufficient. Reuse the existing plan and evidence, not extra checklists.
|
|
22
|
+
|
|
23
|
+
## Completion contract
|
|
24
|
+
|
|
25
|
+
1. Define the observable result. Resolve routine choices from current repository
|
|
26
|
+
evidence; ask only about consequential uncertainty in intent or authorization.
|
|
27
|
+
2. Trace the real entry point, callers and effects. Include required wiring,
|
|
28
|
+
delivery steps and checks; preserve unrelated work and compatibility.
|
|
29
|
+
3. Make the smallest complete change. Handle relevant boundaries, errors,
|
|
30
|
+
security and resource ownership. Define expected results before implementation;
|
|
31
|
+
add regression coverage for material behavior, reuse adequate existing checks.
|
|
32
|
+
4. Run required checks and focused verification through the changed entry point.
|
|
33
|
+
Broaden for shared contracts; rerun checks invalidated by edits. A helper test
|
|
34
|
+
alone does not prove delivery. Never weaken checks to hide failure.
|
|
35
|
+
5. Review the complete diff, including new files. Report behavior, checks/results,
|
|
36
|
+
assumptions and unverified paths. Distinguish source from deployed/runtime
|
|
37
|
+
evidence. Continue authorized work; stop only on completion or a concrete blocker.
|
|
38
|
+
|
|
39
|
+
## Read only for the current risk
|
|
40
|
+
|
|
41
|
+
A bounded change with clear callers and checks needs only this core. Otherwise
|
|
42
|
+
read the matching reference, one at a time; never preload the set or reread merely
|
|
43
|
+
because the phase changed. Select repository excerpts by relevant symbols/ranges.
|
|
44
|
+
|
|
45
|
+
| Read when | Reference |
|
|
46
|
+
| --- | --- |
|
|
47
|
+
| Scope, callers or integration are unclear | [Discovery](references/discovery-and-scope.md) |
|
|
48
|
+
| Inputs, effects, lifetime or compatibility change | [Boundaries](references/boundaries-and-lifecycle.md) |
|
|
49
|
+
| Evidence or delivery is uncertain | [Verification](references/verification-and-completion.md) |
|
|
50
|
+
| A check fails or progress stalls; before changing strategy | [Recovery](references/failure-recovery.md) |
|
|
51
|
+
|
|
52
|
+
Never retry an unchanged failed operation. Reference deferral does not waive the
|
|
53
|
+
core obligations. Follow the router's other applicable contracts without duplicating them.
|
|
54
|
+
<!-- /kiokuko:runtime -->
|
|
@@ -0,0 +1,56 @@
|
|
|
1
|
+
<!-- KIOKUKO MANAGED STANDARD SKILL: one-shot-software-completion -->
|
|
2
|
+
|
|
3
|
+
# Boundaries and lifecycle
|
|
4
|
+
|
|
5
|
+
Use when changing input acceptance, effects, state or a public/stored contract.
|
|
6
|
+
Apply the code Skill's selected experts; this reference helps find omissions
|
|
7
|
+
across the workflow rather than replacing those contracts.
|
|
8
|
+
|
|
9
|
+
## Derive cases from the actual contract
|
|
10
|
+
|
|
11
|
+
Select relevant boundaries; do not build an exhaustive speculative matrix.
|
|
12
|
+
Each selected case needs deliberate accept/reject behavior or a demonstrated
|
|
13
|
+
upstream invariant. A type assertion alone does not validate external input.
|
|
14
|
+
|
|
15
|
+
| Input or boundary | Candidate cases |
|
|
16
|
+
| --- | --- |
|
|
17
|
+
| Text | absent, empty/whitespace, Unicode, length limit, injection-shaped content |
|
|
18
|
+
| Numbers | zero, negative, bounds, fractional/non-finite values, encoded strings |
|
|
19
|
+
| Collections | empty, singleton, duplicates, order, size limits |
|
|
20
|
+
| Optional fields | missing, null, undefined, present but empty |
|
|
21
|
+
| Identity | nonexistent, deleted, stale, another user/tenant's resource |
|
|
22
|
+
| Time | zone/offset, DST, epoch zero, skew, expiry boundary |
|
|
23
|
+
| Concurrent work | duplicate/out-of-order request, cancellation, partial batch |
|
|
24
|
+
|
|
25
|
+
Example: pagination needs a defined limit range and integer policy, stable
|
|
26
|
+
ordering, cursor behavior and tenant isolation. Whether an unknown cursor is an
|
|
27
|
+
error or an empty page comes from the API contract, not this checklist.
|
|
28
|
+
|
|
29
|
+
## Decide effects and failure semantics
|
|
30
|
+
|
|
31
|
+
For each changed network, filesystem, database or process boundary, identify
|
|
32
|
+
ownership, timeout/cancellation, public error and partial-success behavior.
|
|
33
|
+
Reuse the repository policy; avoid silent catches or a success result after a
|
|
34
|
+
required effect failed. Retries require an idempotent operation or a verified
|
|
35
|
+
deduplication contract, bounded attempts and preserved request identity.
|
|
36
|
+
|
|
37
|
+
A timeout after a write may mean the effect succeeded but its acknowledgment
|
|
38
|
+
was lost. Do not resend a charge, notification or mutation merely because the
|
|
39
|
+
response is absent. Reconcile uncertain state through the supported mechanism.
|
|
40
|
+
|
|
41
|
+
For each resource or state holder, trace creation, access, invalidation, cleanup,
|
|
42
|
+
restart/reload and test teardown. Account for subscriptions, timers, locks,
|
|
43
|
+
caches and background jobs. Preserve transaction and rollback boundaries;
|
|
44
|
+
cancellation of a UI is not proof that the underlying operation stopped.
|
|
45
|
+
|
|
46
|
+
## Preserve consumers
|
|
47
|
+
|
|
48
|
+
Identify contracts that leave this patch: JSON, database rows, queue messages,
|
|
49
|
+
exports, CLI flags, config and environment variables. Preserve existing behavior
|
|
50
|
+
by default. When a breaking change is requested, include its migration/version
|
|
51
|
+
and downstream update strategy within authorized scope.
|
|
52
|
+
|
|
53
|
+
Adding an optional field with a safe default may preserve compatibility;
|
|
54
|
+
renaming, deleting, changing type or redefining defaults may not. Test old data
|
|
55
|
+
and callers where they remain supported. Check readers as well as writers and
|
|
56
|
+
rollout/restart ordering when old and new versions can coexist.
|
|
@@ -0,0 +1,67 @@
|
|
|
1
|
+
<!-- KIOKUKO MANAGED STANDARD SKILL: one-shot-software-completion -->
|
|
2
|
+
|
|
3
|
+
# Discovery and scope
|
|
4
|
+
|
|
5
|
+
Use when the behavioral requirement, caller graph or patch boundary is unclear.
|
|
6
|
+
Keep decisions in the existing plan; a separate document is not required.
|
|
7
|
+
|
|
8
|
+
## Reconstruct the requirement
|
|
9
|
+
|
|
10
|
+
- Express the requested result as observable input, action and output. "Add
|
|
11
|
+
pagination" needs an entry point, response shape, ordering, defaults and
|
|
12
|
+
compatibility with existing callers, not just a pagination helper.
|
|
13
|
+
- Resolve unspecified choices from a working analog, project instructions and
|
|
14
|
+
conventions, then the framework idiom already used locally. Prefer the least
|
|
15
|
+
disruptive reversible choice and record material assumptions. Explicit user
|
|
16
|
+
requirements outrank inferred conventions.
|
|
17
|
+
- Repository evidence cannot answer every ambiguity. Ask when competing
|
|
18
|
+
interpretations materially change the requested result, data, public contract
|
|
19
|
+
or permissions. Complete independent work while a necessary answer is pending.
|
|
20
|
+
Do not treat naming or formatting choices with established defaults as blockers.
|
|
21
|
+
|
|
22
|
+
## Trace before editing
|
|
23
|
+
|
|
24
|
+
Follow entry point -> target -> callees/effects -> callers/consumers. Search
|
|
25
|
+
changed symbols and serialized field names; the compiler cannot find untyped
|
|
26
|
+
fixtures, external consumers or dynamic registrations. Inspect tests and the
|
|
27
|
+
actual check commands. Check imports, module state, exports and nearby helpers
|
|
28
|
+
in contiguous reads; read the whole file when its contract depends on them.
|
|
29
|
+
Avoid recursively reading every transitive dependency without a concrete risk.
|
|
30
|
+
|
|
31
|
+
Use the closest maintained analog for placement, registration, errors, config,
|
|
32
|
+
tests and docs. Recency alone does not make an example correct. Preserve existing
|
|
33
|
+
dependency direction and use local validation, HTTP, IDs, retry and test helpers
|
|
34
|
+
before adding another implementation or dependency.
|
|
35
|
+
|
|
36
|
+
## Find the required accompanying changes
|
|
37
|
+
|
|
38
|
+
From the actual workflow, identify relevant types, validation, serialization,
|
|
39
|
+
permissions, flags, UI strings, CLI help/API docs, fixtures, exports, registration,
|
|
40
|
+
migrations and generated artifacts. Logging and changelog entries are required
|
|
41
|
+
only when the task or repository requires them. For setup and delivery, follow
|
|
42
|
+
the artifact to its consumer and reload trigger with `veteran-programmer-skill`.
|
|
43
|
+
|
|
44
|
+
Example: a new notification provider may require its client/schema, registry
|
|
45
|
+
entry and configuration validation. A provider class tested only in isolation
|
|
46
|
+
does not prove users can select it.
|
|
47
|
+
|
|
48
|
+
## Bound and plan the patch
|
|
49
|
+
|
|
50
|
+
- Include every step required to make the behavior reachable and correct. A
|
|
51
|
+
smaller diff is a tiebreaker between complete solutions.
|
|
52
|
+
- Follow changed contracts through types, stored/wire data, callers, fixtures
|
|
53
|
+
and docs. Keep compatibility where consumers cannot change in this patch;
|
|
54
|
+
intentional compatibility aliases are not stale references to remove.
|
|
55
|
+
- Fix an adjacent defect when the new behavior depends on it, or isolate the
|
|
56
|
+
new path so it does not spread the defect. Record the choice. Stable pagination,
|
|
57
|
+
for example, may need an ID tiebreaker in an existing shared sort.
|
|
58
|
+
- Leave unrelated cleanup alone. A same-file edit or cheap refactor is not by
|
|
59
|
+
itself justification to expand scope. Preserve staged and unstaged user work.
|
|
60
|
+
- Record path -> responsibility -> concrete check. Include expected outputs for
|
|
61
|
+
the main path and material failure cases. Order related edits so checks remain
|
|
62
|
+
interpretable, commonly contracts -> implementation -> wiring -> tests/docs.
|
|
63
|
+
Reassess scope if the plan grows; file count alone cannot decide correctness.
|
|
64
|
+
|
|
65
|
+
Establish focused baseline results when existing failures could obscure the
|
|
66
|
+
change. Inspect shared callers before choosing wider checks; preserve exact
|
|
67
|
+
commands and results so new failures can be attributed rather than guessed.
|
|
@@ -0,0 +1,43 @@
|
|
|
1
|
+
<!-- KIOKUKO MANAGED STANDARD SKILL: one-shot-software-completion -->
|
|
2
|
+
|
|
3
|
+
# Failure recovery
|
|
4
|
+
|
|
5
|
+
Read when a check fails or progress stalls. Recovery stays within the original
|
|
6
|
+
scope, current host role and permissions; it is not an automatic retry policy.
|
|
7
|
+
|
|
8
|
+
## Classify before editing
|
|
9
|
+
|
|
10
|
+
Read the relevant complete error and causal context. Separate observations from
|
|
11
|
+
hypotheses; multiple causes may coexist.
|
|
12
|
+
|
|
13
|
+
| Evidence indicates | Next action |
|
|
14
|
+
| --- | --- |
|
|
15
|
+
| Wrong interpretation of the requirement | Revisit the observable result and material ambiguity |
|
|
16
|
+
| Missed caller, helper contract or integration | Trace that dependency and correct the plan |
|
|
17
|
+
| Local implementation error | Apply a focused fix and its regression check |
|
|
18
|
+
| Environment/tooling failure | Verify the cause; make only an authorized, bounded repair |
|
|
19
|
+
| Failure demonstrated in the baseline | Report it; investigate if it blocks or interacts with the change |
|
|
20
|
+
|
|
21
|
+
If the same failure remains after two targeted fixes, stop making variants of
|
|
22
|
+
the same patch. Create a minimal reproduction or focused diagnostic, revisit
|
|
23
|
+
the input/contract and consider a different approach supported by repository
|
|
24
|
+
evidence. Do not rerun an unchanged failed operation without new information.
|
|
25
|
+
|
|
26
|
+
## Preserve the evidence
|
|
27
|
+
|
|
28
|
+
Do not loosen assertions, skip tests, add broad catches/casts, suppress errors
|
|
29
|
+
or increase timeouts merely to make a failure disappear. Change a check only
|
|
30
|
+
when evidence shows its expectation is wrong and explain that correction.
|
|
31
|
+
|
|
32
|
+
Fix tooling only when it blocks required verification and the repair is within
|
|
33
|
+
scope. Prefer a targeted runnable check when broader infrastructure is missing;
|
|
34
|
+
report exactly what it proves and what remains unverified. Do not rewrite CI,
|
|
35
|
+
install unrelated dependencies or change external configuration to evade a
|
|
36
|
+
blocker. A permission or credential gap is not a prompt to bypass controls.
|
|
37
|
+
|
|
38
|
+
After a repair, rerun the failed check and all checks affected by the new diff,
|
|
39
|
+
then review the final patch again. A signature repair can require caller tests,
|
|
40
|
+
typecheck and runtime integration even if only one test originally failed.
|
|
41
|
+
Stop when requirements are verified or progress requires unavailable evidence,
|
|
42
|
+
access or a consequential user decision. State the blocker and concrete next
|
|
43
|
+
action rather than claiming completion or promising unattended continuation.
|
|
@@ -0,0 +1,62 @@
|
|
|
1
|
+
<!-- KIOKUKO MANAGED STANDARD SKILL: one-shot-software-completion -->
|
|
2
|
+
|
|
3
|
+
# Verification and completion
|
|
4
|
+
|
|
5
|
+
Use when selecting evidence, reviewing a patch or validating its delivery.
|
|
6
|
+
|
|
7
|
+
## Prove behavior at the changed boundary
|
|
8
|
+
|
|
9
|
+
Use commands defined by the repository. Run required checks and choose further
|
|
10
|
+
checks by the affected contract: typecheck, lint, focused tests, relevant
|
|
11
|
+
integration tests, build/package inspection and an actual entry-point exercise.
|
|
12
|
+
Reuse a passing integration test when it already exercises that entry point;
|
|
13
|
+
do not add a redundant live operation merely to tick a runtime checkbox.
|
|
14
|
+
|
|
15
|
+
- State expected outputs before implementation. Check meaningful success and
|
|
16
|
+
failure cases, forbidden effects after rejection, ownership and compatibility.
|
|
17
|
+
- For a regression test, observe failure before the fix or demonstrate that an
|
|
18
|
+
isolated mutation of the defective behavior makes it fail. Do not revert user
|
|
19
|
+
work to create that demonstration. Excessive mocks can hide missing wiring.
|
|
20
|
+
- Exercise the public route, CLI, mounted interaction, migration or package
|
|
21
|
+
consumer that must work. If a fixture substitutes for a live service, identify
|
|
22
|
+
the substitution and the remaining uncertainty.
|
|
23
|
+
- Compare failures with recorded baseline evidence. Do not label a failure
|
|
24
|
+
pre-existing without evidence or infer a product defect from a sandbox/network
|
|
25
|
+
restriction alone.
|
|
26
|
+
- Broaden checks for changed shared callers, public contracts or delivery. After
|
|
27
|
+
a repair, rerun invalidated checks, including integration/build checks affected
|
|
28
|
+
by it. Repeat the full suite only when required or justified by the change.
|
|
29
|
+
|
|
30
|
+
Tests should protect behavior rather than mirror implementation or prose.
|
|
31
|
+
For low-impact mechanical edits, an existing focused check or direct inspection
|
|
32
|
+
may suffice. Missing credentials or unavailable infrastructure must be reported;
|
|
33
|
+
they never turn an unrun check into a pass.
|
|
34
|
+
|
|
35
|
+
## Review the complete patch
|
|
36
|
+
|
|
37
|
+
Read staged, unstaged and new-file changes in scope. For each hunk ask:
|
|
38
|
+
|
|
39
|
+
1. Does it implement the requested observable behavior or required integration?
|
|
40
|
+
2. Which accepted input, failure or caller could make it wrong?
|
|
41
|
+
3. Are error behavior, authorization, cleanup and compatibility preserved?
|
|
42
|
+
4. Is a new function actually reachable through registration/export/binding?
|
|
43
|
+
5. Are placeholders, debug effects, hardcoded secrets/paths, accidental `.only`
|
|
44
|
+
or `.skip`, casts and suppressed checks justified or removed?
|
|
45
|
+
|
|
46
|
+
Inspect generated/snapshot changes rather than accepting churn. Reconcile the
|
|
47
|
+
diff with the plan and accompanying artifacts: present, deliberately omitted
|
|
48
|
+
with a reason, or still missing. A correct helper with no consumer is unfinished.
|
|
49
|
+
If review causes edits, rerun the checks whose evidence those edits invalidate.
|
|
50
|
+
|
|
51
|
+
## Completion decision
|
|
52
|
+
|
|
53
|
+
The request is complete when its observable behavior has matching evidence,
|
|
54
|
+
required integration and compatibility are covered, relevant boundaries and
|
|
55
|
+
failure cases are handled, required checks have no unexplained new failures,
|
|
56
|
+
and the final review has no unresolved issue within scope.
|
|
57
|
+
|
|
58
|
+
Report the changed behavior, material assumptions and repository basis, exact
|
|
59
|
+
checks/results, and any adjacent repair, dependency or breaking change. Name
|
|
60
|
+
unverified runtime/deployment paths, blockers and deliberate exclusions. Distinguish
|
|
61
|
+
source, packaged files, deployed copies and the active process; evidence for one
|
|
62
|
+
does not prove the others. Do not call partially verified delivery fully verified.
|