peaks-loop 4.0.0-beta.8 → 4.0.1

package/dist/cli/commands/skill-loop-engineering-readiness-commands.js

@@ -0,0 +1,173 @@
+/**
+ * `peaks skill lint --category loop-engineering-readiness` — M6 / spec §7.5 + §8.4
+ *
+ * Loop Engineering readiness gate for any new peaks-* skill that
+ * participates in Loop Engineering (crystallization or evolution).
+ *
+ * Usage:
+ *   peaks skill lint --category loop-engineering-readiness --path <skill-dir>
+ *   peaks skill lint --category loop-engineering-readiness --path <skill-dir> --json
+ *
+ * The command:
+ *   1. Resolves <skill-dir>/SKILL.md (default if the path is a file).
+ *   2. Calls lintSkillLoopEngineeringReadiness() with the file contents.
+ *   3. Prints a structured JSON envelope via printResult (or a
+ *      human-readable summary when --json is omitted).
+ *   4. Sets process.exitCode = 1 on a non-ok result, so the LLM
+ *      gate can short-circuit a future peaks-* skill that fails the
+ *      lint.
+ *
+ * The lint asserts three structural properties:
+ *   1. the SKILL.md references
+ *      `.peaks/standards/loop-engineering-guidelines.md`;
+ *   2. the SKILL.md does not introduce a CLI verb the user is meant
+ *      to type (only LLM-coordinated verbs from the sediment /
+ *      asset / evolution surface are allowed; RL-1);
+ *   3. the SKILL.md does not introduce a JSON / manifest
+ *      hand-authoring surface (RL-1).
+ *
+ * The user never types `peaks skill lint …` — the LLM runs it on
+ * the user's behalf. This command is also reachable as
+ * `peaks skill ready --category loop-engineering-readiness
+ *   --path <skill-dir>`
+ * via a small alias added at the bottom of this file.
+ */
+import { readFileSync, existsSync, statSync } from 'node:fs';
+import { join, resolve } from 'node:path';
+import { lintSkillLoopEngineeringReadiness, } from '../../services/standards/loop-engineering-readiness-lint.js';
+import { addJsonOption, getErrorMessage, printResult } from '../cli-helpers.js';
+import { fail, ok } from 'peaks-loop-shared/result';
+export const LOOP_ENGINEERING_READINESS_CATEGORY = 'loop-engineering-readiness';
+/**
+ * Resolve the SKILL.md file path from a `--path <skill-dir>` value.
+ *
+ * Accepts either:
+ *   - a directory containing a SKILL.md (the common case for a
+ *     peaks-* skill: `src/skills/<id>/`, `skills/<id>/`, etc.);
+ *   - a direct file path to a SKILL.md.
+ *
+ * Returns the absolute path to the SKILL.md, or null if no SKILL.md
+ * is found.
+ */
+export function resolveSkillMdPath(rawPath) {
+    const abs = resolve(rawPath);
+    if (!existsSync(abs))
+        return null;
+    const st = statSync(abs);
+    if (st.isFile()) {
+        return abs.toLowerCase().endsWith('skill.md') ? abs : null;
+    }
+    if (st.isDirectory()) {
+        const candidate = join(abs, 'SKILL.md');
+        return existsSync(candidate) ? candidate : null;
+    }
+    return null;
+}
+/**
+ * Pure helper: run the readiness lint against the SKILL.md text and
+ * return a CLI-shaped envelope. Kept separate from the Commander
+ * action so unit + integration tests can drive it without spawning
+ * a child process.
+ */
+export function runReadinessLint(rawPath) {
+    const skillMdPath = resolveSkillMdPath(rawPath);
+    if (!skillMdPath) {
+        return {
+            ok: false,
+            code: 'SKILL_FILE_NOT_FOUND',
+            message: `could not resolve SKILL.md from --path ${rawPath}`,
+            data: { path: rawPath, category: LOOP_ENGINEERING_READINESS_CATEGORY, findings: [] },
+            nextActions: [
+                'Pass a directory containing SKILL.md or a direct path to a SKILL.md file.',
+            ],
+        };
+    }
+    const text = readFileSync(skillMdPath, 'utf-8');
+    const result = lintSkillLoopEngineeringReadiness(text);
+    if (result.ok) {
+        return {
+            ok: true,
+            code: 'SKILL_READINESS_OK',
+            message: 'SKILL.md passes the Loop Engineering readiness lint',
+            data: {
+                path: skillMdPath,
+                category: LOOP_ENGINEERING_READINESS_CATEGORY,
+                findings: [],
+            },
+            nextActions: [
+                'The skill is allowed to participate in Loop Engineering (crystallization / evolution).',
+            ],
+        };
+    }
+    return {
+        ok: false,
+        code: 'SKILL_READINESS_FAILED',
+        message: `SKILL.md failed the Loop Engineering readiness lint (${result.findings.length} finding(s))`,
+        data: {
+            path: skillMdPath,
+            category: LOOP_ENGINEERING_READINESS_CATEGORY,
+            findings: result.findings,
+        },
+        nextActions: [
+            'Address every finding listed in data.findings, then re-run the lint.',
+            'See src/services/standards/loop-engineering-readiness-lint.ts for the rule definitions.',
+            'See .peaks/standards/loop-engineering-guidelines.md for the red lines the lint enforces.',
+        ],
+    };
+}
+function lintAction(options, io) {
+    if (options.category !== LOOP_ENGINEERING_READINESS_CATEGORY) {
+        printResult(io, fail('skill.lint', 'UNKNOWN_LINT_CATEGORY', `only --category ${LOOP_ENGINEERING_READINESS_CATEGORY} is implemented in M6`, { category: options.category ?? null }, [
+            `Pass --category ${LOOP_ENGINEERING_READINESS_CATEGORY}.`,
+        ]), options.json);
+        process.exitCode = 1;
+        return;
+    }
+    if (!options.path) {
+        printResult(io, fail('skill.lint', 'MISSING_PATH', '--path <skill-dir> is required', { category: options.category }, ['Pass --path pointing at a peaks-* skill directory containing SKILL.md.']), options.json);
+        process.exitCode = 1;
+        return;
+    }
+    try {
+        const envelope = runReadinessLint(options.path);
+        if (envelope.ok) {
+            printResult(io, ok('skill.lint', envelope.data, [], envelope.nextActions), options.json);
+            return;
+        }
+        printResult(io, fail('skill.lint', envelope.code, envelope.message, envelope.data, envelope.nextActions), options.json);
+        process.exitCode = 1;
+    }
+    catch (error) {
+        printResult(io, fail('skill.lint', 'SKILL_READINESS_ERROR', getErrorMessage(error), { path: options.path }, ['Verify the path is readable.']), options.json);
+        process.exitCode = 1;
+    }
+}
+export function registerSkillLoopEngineeringReadinessCommands(program, io) {
+    // `peaks skill lint --category loop-engineering-readiness --path <skill-dir>`
+    // — primary surface, named to match the spec §7.5 / §8.4 wording.
+    // We reuse the existing `skill` parent if one is registered; per
+    // the add-a-new-subcommand-check-for-existing-top-level-first rule,
+    // we never re-create `skill` when it's already there.
+    const existingSkill = program.commands.find((c) => c.name() === 'skill');
+    const skill = existingSkill ?? program
+        .command('skill')
+        .description('skill operations (M6: lint --category loop-engineering-readiness)');
+    addJsonOption(skill
+        .command('lint')
+        .description(`M6: lint a peaks-* SKILL.md against a category. Currently supports --category ${LOOP_ENGINEERING_READINESS_CATEGORY} (spec §7.5 / §8.4 / RL-8).`)
+        .option('--category <name>', `lint category; the M6 implementation only supports ${LOOP_ENGINEERING_READINESS_CATEGORY}`, LOOP_ENGINEERING_READINESS_CATEGORY)
+        .requiredOption('--path <skill-dir>', 'path to a peaks-* skill directory (containing SKILL.md) or directly to a SKILL.md file')).action((options) => lintAction(options, io));
+    // `peaks skill ready --category loop-engineering-readiness --path <skill-dir>`
+    // — alias verb chosen by M6 for human-facing callouts. It points at
+    // the same handler; both verbs are first-class so users (LLM
+    // proxies) can pick whichever phrasing fits the conversation.
+    // Per the spec, the user never types either verb; the LLM runs the
+    // CLI on the user's behalf.
+    skill
+        .command('ready')
+        .description(`M6 alias for \`peaks skill lint --category ${LOOP_ENGINEERING_READINESS_CATEGORY}\`; same flags, same exit codes.`)
+        .option('--category <name>', `lint category; the M6 implementation only supports ${LOOP_ENGINEERING_READINESS_CATEGORY}`, LOOP_ENGINEERING_READINESS_CATEGORY)
+        .requiredOption('--path <skill-dir>', 'path to a peaks-* skill directory or SKILL.md file')
+        .option('--json', 'print machine-readable JSON envelope')
+        .action((options) => lintAction(options, io));
+}

package/dist/cli/commands/skill-search-commands.d.ts

@@ -0,0 +1,25 @@
+/**
+ * peaks skill search — CLI primitive for S0 of the 4.0.0-beta.5
+ * peaks-solo dispatcher release.
+ *
+ * Spec: docs/superpowers/specs/2026-07-08-peaks-solo-dispatcher-design.md §3.2
+ * Plan: docs/superpowers/plans/2026-07-08-peaks-solo-dispatcher/s0-skill-search-cli.md
+ *
+ * Wired into the existing `peaks skill` group by
+ * `src/cli/commands/core/skill-command.ts` (one import + one call).
+ * The command ALWAYS emits a JSON array on stdout, even on the
+ * no-match case (which exits 0 with `[]` per plan §"Match rules (v1)").
+ *
+ * Exit codes (locked in plan §"API Contract"):
+ *   0 — success (may be empty array)
+ *   1 — invalid args (Zod validation failure)
+ *   2 — unexpected error (skill pool read fail, etc.)
+ */
+import type { Command } from 'commander';
+import type { ProgramIO } from '../cli-helpers.js';
+/**
+ * Validate the raw CLI flags, call the service, and emit a JSON
+ * envelope on stdout. Errors flow through stderr + non-zero exit
+ * codes per the plan §"API Contract" table.
+ */
+export declare function registerSkillSearchCommand(program: Command, io: ProgramIO): void;

package/dist/cli/commands/skill-search-commands.js

@@ -0,0 +1,71 @@
+import { searchSkills, SkillSearchInputSchema } from '../../services/skill/skill-search-service.js';
+import { getErrorMessage } from 'peaks-loop-shared/result';
+/**
+ * Validate the raw CLI flags, call the service, and emit a JSON
+ * envelope on stdout. Errors flow through stderr + non-zero exit
+ * codes per the plan §"API Contract" table.
+ */
+export function registerSkillSearchCommand(program, io) {
+    // The parent `skill` command is created by registerSkillCommand in
+    // core/skill-command.ts. To keep the wiring self-contained we
+    // resolve the parent by name; this also lets tests register the
+    // subcommand in isolation.
+    const skill = program.commands.find((c) => c.name() === 'skill');
+    if (skill === undefined) {
+        // Defensive: the parent must be registered before us. Surface the
+        // error visibly — the dispatcher cannot triage without `peaks skill`
+        // existing, so the LLM-side caller needs to know.
+        throw new Error('peaks skill search: parent `skill` command not found. ' +
+            'Ensure registerSkillCommand is called before registerSkillSearchCommand.');
+    }
+    skill
+        .command('search')
+        .description('Search the in-tree skill pool by --query (substring on description + triggers) ' +
+        'and/or --tag (exact match on metadata.tags) and/or --domain (exact match). ' +
+        'Outputs a JSON array (always, even on no-match) to stdout. ' +
+        'See docs/superpowers/specs/2026-07-08-peaks-solo-dispatcher-design.md §3.2.')
+        .option('-q, --query <text>', 'case-insensitive substring matched against skill description + triggers')
+        .option('-t, --tag <tag>', 'exact match on metadata.tags (e.g. "orchestrator", "loop-engineering")')
+        .option('-d, --domain <domain>', 'exact match on metadata.domain (locked enum: code | content | doctor | research | triage | sop | audit | final-review | resume | status | test | ide | slice-decompose | issue-fix-orchestrator | perf-audit | security-audit | reviewer)')
+        .option('-l, --limit <n>', 'max results returned (1..100, default 20)', (v) => Number.parseInt(v, 10))
+        .option('--include-internal', 'include skills with visibility: internal (default: hide them)')
+        .action(async (options) => {
+        // 1) Coerce + validate input via the service's Zod schema.
+        //    The schema's refine rejects empty input — that is the
+        //    "all-empty → error" contract the spec mandates.
+        const raw = {};
+        if (options.query !== undefined)
+            raw['query'] = options.query;
+        if (options.tag !== undefined)
+            raw['tag'] = options.tag;
+        if (options.domain !== undefined)
+            raw['domain'] = options.domain;
+        if (options.limit !== undefined)
+            raw['limit'] = options.limit;
+        if (options.includeInternal === true)
+            raw['includeInternal'] = true;
+        const parsed = SkillSearchInputSchema.safeParse(raw);
+        if (!parsed.success) {
+            // Exit code 1 = invalid args. Emit a human-readable message
+            // on stderr so the LLM-side caller can act on it; do NOT
+            // pollute stdout (which downstream tools parse as JSON).
+            for (const issue of parsed.error.issues) {
+                io.stderr(`${issue.path.join('.') || '<root>'}: ${issue.message}`);
+            }
+            process.exitCode = 1;
+            return;
+        }
+        // 2) Call the service. Any unexpected error (skill pool read
+        //    fail, etc.) maps to exit code 2.
+        try {
+            const results = await searchSkills(parsed.data);
+            // Always emit a JSON array on stdout. The plan locks this
+            // contract: even no-match returns `[]`, never `null`.
+            io.stdout(JSON.stringify(results));
+        }
+        catch (error) {
+            io.stderr(`skill.search failed: ${getErrorMessage(error)}`);
+            process.exitCode = 2;
+        }
+    });
+}

package/dist/cli/commands/skill-visibility.d.ts

@@ -0,0 +1,8 @@
+import type { Command } from 'commander';
+export interface SkillVisibility {
+    name: string;
+    userInvocable: boolean;
+    visibility: 'public' | 'internal';
+}
+export declare function listSkillsVisibility(repoRoot: string): SkillVisibility[];
+export declare function registerSkillVisibilityCommand(program: Command, repoRoot: string): void;

package/dist/cli/commands/skill-visibility.js

@@ -0,0 +1,63 @@
+/**
+ * `peaks skill:visibility` — Skill visibility CLI surface.
+ *
+ * Slice: Task 1 of peaks-code → peaks-code rename plan.
+ *
+ * Reads `.claude-plugin/marketplace.json`, resolves each skill entry's
+ * visibility (public / internal) from the optional `userInvocable`
+ * field, and emits either:
+ *   - a TSV list (`name \t visibility`) for human use
+ *   - a JSON envelope `{ ok, skills }` for programmatic use
+ *
+ * Schema contract:
+ *   - internal: `userInvocable: false`
+ *   - public (default): `userInvocable` omitted OR `true`
+ *
+ * The skill list lives at `plugins[0].skills` in marketplace.json;
+ * entries are objects of shape `{ name, path?, userInvocable?, description? }`.
+ * Older string-array shapes are auto-coerced (each string is treated as
+ * a public skill whose name is the basename of the path).
+ */
+import { readFileSync } from 'node:fs';
+import { join, basename } from 'node:path';
+export function listSkillsVisibility(repoRoot) {
+    const marketplacePath = join(repoRoot, '.claude-plugin', 'marketplace.json');
+    const raw = readFileSync(marketplacePath, 'utf-8');
+    const parsed = JSON.parse(raw);
+    const skills = parsed.plugins?.[0]?.skills ?? [];
+    return skills.map((entry) => {
+        if (typeof entry === 'string') {
+            return {
+                name: basename(entry),
+                userInvocable: true,
+                visibility: 'public',
+            };
+        }
+        const userInvocable = entry.userInvocable !== false;
+        return {
+            name: entry.name ?? '',
+            userInvocable,
+            visibility: userInvocable ? 'public' : 'internal',
+        };
+    });
+}
+export function registerSkillVisibilityCommand(program, repoRoot) {
+    const cmd = program
+        .command('skill:visibility')
+        .description('List skill visibility (public vs internal)')
+        .option('--list', 'List all skills')
+        .option('--name <name>', 'Query single skill')
+        .option('--json', 'JSON output');
+    cmd.action((opts) => {
+        const all = listSkillsVisibility(repoRoot);
+        const filtered = opts.name ? all.filter((s) => s.name === opts.name) : all;
+        if (opts.json) {
+            process.stdout.write(JSON.stringify({ ok: true, skills: filtered }, null, 2) + '\n');
+        }
+        else {
+            for (const s of filtered) {
+                process.stdout.write(`${s.name}\t${s.visibility}\n`);
+            }
+        }
+    });
+}

package/dist/cli/commands/slice-commands.d.ts

@@ -0,0 +1,24 @@
+import { Command } from 'commander';
+import { type ProgramIO } from '../cli-helpers.js';
+export declare function registerSliceCommands(program: Command, io: ProgramIO): void;
+interface PickedEnvelope {
+    readonly rid: string;
+    readonly picked: readonly {
+        readonly rid: string;
+        readonly files: readonly string[];
+        readonly label: string;
+    }[];
+}
+/**
+ * Validate a -picked.json envelope. Throws a CLI-friendly Error on any
+ * shape violation; the catch in the slice.plan action converts it to
+ * a fail() envelope with `code: 'PICKED_ENVELOPE_INVALID'`.
+ *
+ * Schema:
+ *   { rid: string; picked: Array<{ rid, files: string[], label }> }
+ *
+ * Rejects: missing rid, missing/invalid picked array, picked[i] missing
+ * rid / files / label, picked[i].files empty.
+ */
+export declare function parsePickedFile(pickedPath: string): PickedEnvelope;
+export {};