@gobing-ai/knowledge-kit 0.0.7 → 0.0.8

package/plugins/publishings/zenn-pub/src/index.ts

@@ -1,10 +1,10 @@
-import { mkdir, readFile, rm, writeFile } from 'node:fs/promises';
 import { homedir } from 'node:os';
 import { dirname, join } from 'node:path';
 import { parseArgs } from 'node:util';
 import { type Content, ContentSchema, type Result, ResultSchema } from '@gobing-ai/kk-core';
 import { FakeFileCliTransport, type PublishTransport, type PublishTransportPayload } from '@gobing-ai/publish-harness';
-import { logger } from '@gobing-ai/utils';
+import { createNodeFileSystem } from '@gobing-ai/ts-runtime';
+import { echoError } from '@gobing-ai/ts-utils';
 
 /**
  * Converts a string into a lowercase hyphenated tag (slug) per the publish spec tags convention.
@@ -163,7 +163,7 @@ export class ZennCliFileCliTransport implements PublishTransport {
         const repoPath = repo.startsWith('~') ? join(homedir(), repo.slice(2)) : repo;
 
         try {
-            await mkdir(repoPath, { recursive: true });
+            await createNodeFileSystem().ensureDir(repoPath);
 
             const cliArgs = ['--yes', 'zenn', 'new:article', '--slug', slug, '--title', title, '--type', type];
             if (emoji) {
@@ -179,9 +179,9 @@ export class ZennCliFileCliTransport implements PublishTransport {
             }
 
             const articleDir = join(repoPath, 'articles');
-            await mkdir(articleDir, { recursive: true });
+            await createNodeFileSystem().ensureDir(articleDir);
             const articlePath = join(articleDir, `${slug}.md`);
-            await writeFile(articlePath, markdown, 'utf-8');
+            await createNodeFileSystem().writeFile(articlePath, markdown);
 
             if (published) {
                 const gitSteps: string[][] = [
@@ -246,9 +246,9 @@ export function getPublishTransport(): PublishTransport {
 async function writePublishResult(outputPath: string, result: Result): Promise<void> {
     const outDir = dirname(outputPath);
     if (outDir && outDir !== '.') {
-        await mkdir(outDir, { recursive: true });
+        await createNodeFileSystem().ensureDir(outDir);
     }
-    await writeFile(outputPath, JSON.stringify(result, null, 2), 'utf-8');
+    await createNodeFileSystem().writeFile(outputPath, JSON.stringify(result, null, 2));
 }
 
 /**
@@ -262,11 +262,11 @@ export async function processPublishIO(
     outputPath: string,
     transport: PublishTransport = getPublishTransport(),
 ): Promise<void> {
-    await rm(outputPath, { force: true });
+    await createNodeFileSystem().deleteFile(outputPath);
 
     let content: Content;
     try {
-        const rawInput = await readFile(inputPath, 'utf-8');
+        const rawInput = await createNodeFileSystem().readFile(inputPath);
         content = ContentSchema.parse(JSON.parse(rawInput));
     } catch (error: unknown) {
         const message = `Invalid Content input: ${error instanceof Error ? error.message : String(error)}`;
@@ -292,7 +292,7 @@ export async function main(): Promise<number> {
     });
 
     if (!values.in || !values.out) {
-        logger.error('Missing required arguments: --in and --out');
+        echoError('Missing required arguments: --in and --out');
         return 1;
     }
 
@@ -300,7 +300,7 @@ export async function main(): Promise<number> {
         await processPublishIO(values.in, values.out);
         return 0;
     } catch (error: unknown) {
-        logger.error(`zenn-pub failed: ${error instanceof Error ? error.message : String(error)}`);
+        echoError(`zenn-pub failed: ${error instanceof Error ? error.message : String(error)}`);
         return 1;
     }
 }

package/plugins/kk/agents/judge-compliance.md

@@ -1,37 +0,0 @@
----
-name: judge-compliance
-description: This specialized judge agent should be used when evaluating generated content for regulatory, legal, or safety compliance — prohibited claims, required disclosures, jurisdictional rules, and PII/sensitive-data leakage. Triggers on "compliance check", "legal review of content", "check prohibited claims", "verify disclosures", "regulatory gate", or when a spur workflow needs a compliance evaluation gate before publishing. Delegates all evaluation logic to the judge fat skill with the compliance rubric pre-selected.
-tools: Read, Grep, Glob
----
-
-# judge-compliance — compliance judge persona
-
-Thin wrapper around the **judge** fat skill. Fixes the rubric to `compliance` and forwards
-evaluation. Do not duplicate evaluation logic here — the skill owns it.
-
-## Behavior
-
-1. Receive the content path and the jurisdiction/policy config from the caller or workflow step.
-2. Invoke the `judge` skill procedure with `rubric: compliance`.
-3. Return the verdict JSON path; the skill writes the verdict file.
-
-## Invocation contract
-
-When invoked by an `agent.run` workflow step:
-
-```
-You are the judge-compliance persona.
-Load the judge skill from plugins/kk/skills/judge/SKILL.md.
-Evaluate the content at {{content_path}} against the compliance rubric
-  (plugins/kk/skills/judge/references/rubrics.md, section "compliance").
-Jurisdiction/policy: {{jurisdiction}}      # e.g. US-SEC, EU-GDPR, CN-CAC; or "unspecified"
-Write the verdict JSON to {{verdict_path}} per the contract in SKILL.md.
-Print the verdict path as the last line of stdout.
-```
-
-## Rubric
-
-`compliance` — must-pass: `no-prohibited-claims`, `disclosure-presence`, `jurisdictional-rules`.
-A single prohibited claim is an immediate `FAIL` regardless of score. `pass_threshold = 0.85`.
-Full criteria and evaluation notes (including no-jurisdiction fallback) in the skill's
-`references/rubrics.md`.

package/plugins/kk/agents/judge-tech.md

@@ -1,35 +0,0 @@
----
-name: judge-tech
-description: This specialized judge agent should be used when evaluating generated technical content for factual accuracy, citation integrity, and code correctness. Triggers on "check technical accuracy", "verify tech content", "fact-check technical", "review code samples in content", or when a spur workflow needs a technical-accuracy evaluation gate. Delegates all evaluation logic to the judge fat skill with the tech-accuracy rubric pre-selected.
-tools: Read, Grep, Glob
----
-
-# judge-tech — technical-accuracy judge persona
-
-Thin wrapper around the **judge** fat skill. Fixes the rubric to `tech-accuracy` and forwards
-evaluation. Do not duplicate evaluation logic here — the skill owns it.
-
-## Behavior
-
-1. Receive the content path (and optional verdict output path) from the caller or workflow step.
-2. Invoke the `judge` skill procedure with `rubric: tech-accuracy`.
-3. Return the verdict JSON path; the skill writes the verdict file.
-
-## Invocation contract
-
-When invoked by an `agent.run` workflow step:
-
-```
-You are the judge-tech persona.
-Load the judge skill from plugins/kk/skills/judge/SKILL.md.
-Evaluate the content at {{content_path}} against the tech-accuracy rubric
-  (plugins/kk/skills/judge/references/rubrics.md, section "tech-accuracy").
-Write the verdict JSON to {{verdict_path}} per the contract in SKILL.md.
-Print the verdict path as the last line of stdout.
-```
-
-## Rubric
-
-`tech-accuracy` — must-pass: `factual-correctness`, `no-fabricated-citations`,
-`code-correctness`. `pass_threshold = 0.80`. Full criteria and evaluation notes in the skill's
-`references/rubrics.md`.

package/plugins/kk/agents/judge-tone.md

@@ -1,37 +0,0 @@
----
-name: judge-tone
-description: This specialized judge agent should be used when evaluating generated content for brand voice and tone consistency, banned-phrase compliance, and audience fit. Triggers on "check brand tone", "review voice consistency", "tone audit", "style guide check", or when a spur workflow needs a brand-tone evaluation gate before publishing. Delegates all evaluation logic to the judge fat skill with the brand-tone rubric pre-selected.
-tools: Read, Grep, Glob
----
-
-# judge-tone — brand-tone judge persona
-
-Thin wrapper around the **judge** fat skill. Fixes the rubric to `brand-tone` and forwards
-evaluation. Do not duplicate evaluation logic here — the skill owns it.
-
-## Behavior
-
-1. Receive the content path and the brand config (tone profile + banned-phrase list) from the
-   caller or workflow step.
-2. Invoke the `judge` skill procedure with `rubric: brand-tone`.
-3. Return the verdict JSON path; the skill writes the verdict file.
-
-## Invocation contract
-
-When invoked by an `agent.run` workflow step:
-
-```
-You are the judge-tone persona.
-Load the judge skill from plugins/kk/skills/judge/SKILL.md.
-Evaluate the content at {{content_path}} against the brand-tone rubric
-  (plugins/kk/skills/judge/references/rubrics.md, section "brand-tone").
-Brand config (tone profile + banned phrases): {{brand_config}}
-Write the verdict JSON to {{verdict_path}} per the contract in SKILL.md.
-Print the verdict path as the last line of stdout.
-```
-
-## Rubric
-
-`brand-tone` — must-pass: `tone-consistency`, `banned-phrase-compliance`. `pass_threshold = 0.70`.
-Full criteria and evaluation notes (including no-config fallback) in the skill's
-`references/rubrics.md`.