@ai-content-space/loopx 0.2.0 → 0.2.1

package/plugins/loopx/scripts/plugin-install.test.mjs

@@ -1,125 +0,0 @@
-import { describe, it } from 'node:test';
-import assert from 'node:assert/strict';
-import { execFile } from 'node:child_process';
-import { mkdtemp, readdir, readFile } from 'node:fs/promises';
-import { promisify } from 'node:util';
-import { tmpdir } from 'node:os';
-import { dirname, join, resolve } from 'node:path';
-import { fileURLToPath } from 'node:url';
-
-import { LOOPX_BUNDLED_SKILLS, verifyInstallState } from '../../../src/install-discovery.mjs';
-
-const execFileAsync = promisify(execFile);
-const MODULE_DIR = dirname(fileURLToPath(import.meta.url));
-const PLUGIN_ROOT = resolve(MODULE_DIR, '..');
-const REPO_ROOT = resolve(PLUGIN_ROOT, '..', '..');
-const MANIFEST_PATH = join(PLUGIN_ROOT, '.codex-plugin', 'plugin.json');
-const INSTALL_SCRIPT = join(MODULE_DIR, 'plugin-install.mjs');
-const ROOT_SKILLS_DIR = join(REPO_ROOT, 'skills');
-const PLUGIN_SKILLS_DIR = join(PLUGIN_ROOT, 'skills');
-const LOOPX_SKILLS = LOOPX_BUNDLED_SKILLS;
-
-function loopxEnv(home) {
-  return {
-    ...process.env,
-    HOME: home,
-    LOOPX_HOME: home,
-    LOOPX_AGENTS_ROOT: join(home, '.agents'),
-    LOOPX_SKILLS_ROOT: join(home, '.agents', 'skills'),
-    LOOPX_SKILL_LOCK_PATH: join(home, '.agents', '.skill-lock.json'),
-    LOOPX_PROJECT_ROOT: REPO_ROOT,
-    LOOPX_SKILL_SOURCE_ROOT: PLUGIN_SKILLS_DIR,
-  };
-}
-
-describe('loopx plugin shell', () => {
-  it('defines a plugin manifest that only references plugin-root-relative assets', async () => {
-    const manifest = JSON.parse(await readFile(MANIFEST_PATH, 'utf8'));
-    const packageJson = JSON.parse(await readFile(join(REPO_ROOT, 'package.json'), 'utf8'));
-    const codexPluginEntries = await readdir(join(PLUGIN_ROOT, '.codex-plugin'));
-
-    assert.deepEqual(codexPluginEntries.sort(), ['plugin.json']);
-    assert.equal(manifest.name, 'loopx');
-    assert.equal(manifest.version, packageJson.version);
-    assert.equal(manifest.skills, './skills/');
-    assert.equal(manifest.interface.displayName, 'loopx');
-
-    for (const key of ['skills', 'mcpServers', 'apps']) {
-      if (typeof manifest[key] === 'string') {
-        assert.equal(manifest[key].startsWith('./'), true, `${key} must stay plugin-root-relative`);
-      }
-    }
-  });
-
-  it('mirrors the canonical loopx skill payload into the plugin shell', async () => {
-    for (const skillName of LOOPX_SKILLS) {
-      const rootSkill = await readFile(join(ROOT_SKILLS_DIR, skillName, 'SKILL.md'), 'utf8');
-      const pluginSkill = await readFile(join(PLUGIN_SKILLS_DIR, skillName, 'SKILL.md'), 'utf8');
-      assert.equal(rootSkill.startsWith('---\n'), true, `${skillName} root skill must start with YAML frontmatter`);
-      assert.equal(pluginSkill.startsWith('---\n'), true, `${skillName} plugin skill must start with YAML frontmatter`);
-      assert.equal(pluginSkill, rootSkill, skillName);
-    }
-  });
-
-  it('locks plan as the canonical implementation-planning contract', async () => {
-    const planSkill = await readFile(join(ROOT_SKILLS_DIR, 'plan', 'SKILL.md'), 'utf8');
-    const pluginPlanSkill = await readFile(join(PLUGIN_SKILLS_DIR, 'plan', 'SKILL.md'), 'utf8');
-
-    assert.match(planSkill, /Bite-Sized Task Granularity/);
-    assert.match(planSkill, /No Placeholders/);
-    assert.match(planSkill, /docs\/loopx\/plans\/YYYY-MM-DD-<feature-name>\.md/);
-    assert.match(planSkill, /loopx:subagent-exec/);
-    assert.doesNotMatch(planSkill, /Planner -> Architect -> Critic/);
-    assert.doesNotMatch(planSkill, /consensus-first/i);
-    assert.equal(pluginPlanSkill, planSkill);
-  });
-
-  it('locks clarify to use the conditional spec or plan handoff gate', async () => {
-    const clarifySkill = await readFile(join(ROOT_SKILLS_DIR, 'clarify', 'SKILL.md'), 'utf8');
-    const pluginClarifySkill = await readFile(join(PLUGIN_SKILLS_DIR, 'clarify', 'SKILL.md'), 'utf8');
-
-    assert.equal(pluginClarifySkill, clarifySkill);
-    assert.match(clarifySkill, /needs_spec/);
-    assert.match(clarifySkill, /direct_to_plan/);
-    assert.match(clarifySkill, /docs\/loopx\/design\/<需求名>需求设计文档\.md/);
-    assert.match(clarifySkill, /docs\/loopx\/plans\/YYYY-MM-DD-<feature-name>\.md/);
-    assert.doesNotMatch(clarifySkill, /Recommended invocation: `\$spec/);
-    assert.doesNotMatch(clarifySkill, /Default handoff after normal loopx clarify: `\$plan <slug>`/);
-    assert.doesNotMatch(clarifySkill, /hand off to `build` only/i);
-    assert.doesNotMatch(clarifySkill, /direct execution/i);
-    assert.doesNotMatch(clarifySkill, /direct implementation/i);
-    assert.doesNotMatch(clarifySkill, /directly to implementation/i);
-    assert.doesNotMatch(clarifySkill, /Proceed directly to implementation/i);
-  });
-
-  it('reuses the shared install core while materializing skills from the plugin shell', async () => {
-    const home = await mkdtemp(join(tmpdir(), 'loopx-plugin-home-'));
-    const env = loopxEnv(home);
-
-    await execFileAsync(process.execPath, [INSTALL_SCRIPT], {
-      cwd: REPO_ROOT,
-      env,
-    });
-
-    const inspection = await verifyInstallState(env);
-    assert.equal(inspection.ok, true);
-    for (const skillName of LOOPX_SKILLS) {
-      const installedSkill = await readFile(join(home, '.agents', 'skills', skillName, 'SKILL.md'), 'utf8');
-      const pluginSkill = await readFile(join(PLUGIN_SKILLS_DIR, skillName, 'SKILL.md'), 'utf8');
-      assert.equal(installedSkill, pluginSkill, skillName);
-      assert.equal(inspection.inspection.skills[skillName].registryRow.installationIdentity, 'loopx');
-      assert.equal(inspection.inspection.skills[skillName].registryRow.distributionChannel, 'plugin');
-      assert.equal(inspection.inspection.skills[skillName].registryRow.sourceUrl, PLUGIN_ROOT);
-      assert.equal(
-        inspection.inspection.skills[skillName].registryRow.provenance.some(
-          (entry) => entry.distributionChannel === 'plugin' && entry.sourceUrl === PLUGIN_ROOT,
-        ),
-        true,
-      );
-    }
-
-    const installedSpecTemplate = await readFile(join(home, '.agents', 'skills', 'spec', 'DESIGN_SPEC_TEMPLATE.md'), 'utf8');
-    const pluginSpecTemplate = await readFile(join(PLUGIN_SKILLS_DIR, 'spec', 'DESIGN_SPEC_TEMPLATE.md'), 'utf8');
-    assert.equal(installedSpecTemplate, pluginSpecTemplate);
-  });
-});

package/skills/ai-slop-cleaner/SKILL.md

@@ -1,114 +0,0 @@
----
-name: ai-slop-cleaner
-description: Run an anti-slop cleanup/refactor/deslop workflow
----
-
-# AI Slop Cleaner Skill
-
-Reduce AI-generated slop with a regression-tests-first, smell-by-smell cleanup workflow that preserves behavior and raises signal quality.
-
-## When to Use
-
-Use this skill when:
-- A code path works but feels bloated, noisy, repetitive, or over-abstracted
-- A user asks to “cleanup”, “refactor”, or “deslop” AI-generated output
-- Follow-up implementation left duplicate code, dead code, weak boundaries, missing tests, or unnecessary wrapper layers
-- You need a disciplined cleanup workflow without broad rewrites
-
-## GPT-5.4 Guidance Alignment
-
-- Keep outputs concise and evidence-dense unless risk or the user requests more detail.
-- Treat newer user instructions as local workflow updates without discarding earlier non-conflicting constraints.
-- Keep using inspection, tests, diagnostics, and verification until the cleanup is grounded.
-- Proceed automatically through clear, reversible cleanup steps; ask only when a choice materially changes scope or behavior.
-
-## Scoped File Lists and Ralph Workflow
-
-- This skill can accept a **file list scope** instead of a whole feature area.
-- When the caller provides a changed-files list (for example, Ralph session-owned edits), keep the cleanup strictly bounded to those files.
-- In the **Ralph workflow**, the mandatory deslop pass should run this skill on Ralph's changed files only, in standard mode unless the caller explicitly requests otherwise.
-
-## Procedure
-
-1. **Lock behavior with regression tests first**
-   - Identify the behavior that must not change
-   - Add or run targeted regression tests before editing cleanup candidates
-   - If behavior is currently untested, create the narrowest test coverage needed first
-
-2. **Create a cleanup plan before code**
-   - List the specific smells to remove
-   - Bound the pass to the requested files/scope
-   - If a file list scope is provided, keep the pass restricted to that changed-files list
-   - Order fixes from safest/highest-signal to riskiest
-   - Do not start coding until the cleanup plan is explicit
-
-3. **Categorize issues before editing**
-   - **Duplication** — repeated logic, copy-paste branches, redundant helpers
-   - **Dead code** — unused code, unreachable branches, stale flags, debug leftovers
-   - **Needless abstraction** — pass-through wrappers, speculative indirection, single-use helper layers
-   - **Boundary violations** — hidden coupling, leaky responsibilities, wrong-layer imports or side effects
-   - **Missing tests** — behavior not locked, weak regression coverage, gaps around edge cases
-
-4. **Execute passes one smell at a time**
-   - **Pass 1: Dead code deletion**
-   - **Pass 2: Duplicate removal**
-   - **Pass 3: Naming/error handling cleanup**
-   - **Pass 4: Test reinforcement**
-   - Re-run targeted verification after each pass
-   - Avoid bundling unrelated refactors into the same edit set
-
-5. **Run quality gates**
-   - Regression tests stay green
-   - Lint passes
-   - Typecheck passes
-   - Relevant unit/integration tests pass
-   - Static/security scan passes when available
-   - Diff stays minimal and scoped
-   - No new abstractions or dependencies unless explicitly required
-
-6. **Finish with an evidence-dense report**
-   - Changed files
-   - Simplifications made
-   - Tests/diagnostics/build checks run
-   - Remaining risks
-   - Residual follow-ups or consciously deferred cleanup
-
-## Output Format
-
-```text
-AI SLOP CLEANUP REPORT
-======================
-
-Scope: [files or feature area]
-Behavior Lock: [targeted regression tests added/run]
-Cleanup Plan: [bounded smells and order]
-
-Passes Completed:
-1. Pass 1: Dead code deletion - [concise fix]
-2. Pass 2: Duplicate removal - [concise fix]
-3. Pass 3: Naming/error handling cleanup - [concise fix]
-4. Pass 4: Test reinforcement - [concise fix]
-
-Quality Gates:
-- Regression tests: PASS/FAIL
-- Lint: PASS/FAIL
-- Typecheck: PASS/FAIL
-- Tests: PASS/FAIL
-- Static/security scan: PASS/FAIL or N/A
-
-Changed Files:
-- [path] - [simplification]
-
-Remaining Risks:
-- [none or short deferred item]
-```
-
-## Scenario Examples
-
-**Good:** The user says `continue` after tests already lock behavior and the next smell pass is clear. Continue with the next bounded cleanup pass.
-
-**Good:** The user narrows the scope to a specific file after planning. Keep the regression-tests-first workflow, but apply the new scope locally.
-
-**Bad:** Start rewriting architecture before protecting behavior with tests.
-
-**Bad:** Collapse multiple smell categories into one large refactor with no intermediate verification.

package/skills/autoresearch/SKILL.md

@@ -1,68 +0,0 @@
----
-name: autoresearch
-description: Stateful validator-gated research loop with native-hook persistence
----
-
-# Autoresearch
-
-Autoresearch is the skill-first replacement for the deprecated `omx autoresearch` command.
-It keeps the useful measured-research loop, but it now runs as a native-hook stateful workflow instead of a direct CLI or tmux launch surface.
-
-## Use when
-- You want a Ralph-ish persistent research loop
-- The task should keep nudging until explicit validation evidence exists
-- You want init-time choice between script validation and prompt+architect validation
-
-## Do not use when
-- You want the old `omx autoresearch` command surface (hard-deprecated)
-- You want detached tmux or split-pane launch parity
-- You have not decided the validation regime yet
-
-## Core contract
-1. **Init chooses validation mode.** Pick exactly one:
-   - `mission-validator-script`
-   - `prompt-architect-artifact`
-2. **Persist mode state** in `.omx/state/.../autoresearch-state.json` including:
-   - `validation_mode`
-   - `completion_artifact_path`
-   - `mission_validator_command` **or** `validator_prompt`
-   - optional `output_artifact_path`
-3. **Completion is artifact-gated.** The loop does not stop because the model says “done”, because a stop hook fired once, or because several turns were no-ops.
-4. **Direct CLI launch is gone.** Use `$deep-interview --autoresearch` for intake and `$autoresearch` for execution.
-
-## Completion artifact contract
-
-### `mission-validator-script`
-The completion artifact must exist and record a passing validator result, for example:
-
-```json
-{
-  "status": "passed",
-  "passed": true,
-  "summary": "metric improved beyond baseline"
-}
-```
-
-### `prompt-architect-artifact`
-The completion artifact must include both an architect approval verdict and an output artifact path, for example:
-
-```json
-{
-  "validator_prompt": "Review the research output against the mission.",
-  "architect_review": { "verdict": "approved" },
-  "output_artifact_path": ".omx/specs/autoresearch-demo/report.md"
-}
-```
-
-## Recommended flow
-1. Run `$deep-interview --autoresearch` to clarify mission + evaluator.
-2. Materialize `.omx/specs/autoresearch-{slug}/mission.md`, `sandbox.md`, and `result.json`.
-3. Start `$autoresearch` with the chosen validation mode stored in mode state.
-4. Let stop-hook / auto-nudge continue until the completion artifact satisfies the chosen validation mode.
-5. Finish only after the validator artifact is complete.
-
-## Migration note
-- `omx autoresearch` is hard-deprecated.
-- No direct CLI launch.
-- No tmux split-pane launch.
-- No noop-count completion gate.