reviewer-harness 1.2.0 → 1.3.0

package/README.md

@@ -176,10 +176,12 @@ Reusable playbooks, enabled per project:
 - `skills add <name>` — install into the project and enable it in the config
 - `skills remove <name>` — disable it
 
-Bundled: `safe-editing`, `no-hallucination`, `debug-first`, `explain-bisaya`. Enabled skills render below the rules in every instruction file — and sync also generates a **slash command** for each one (`.opencode/commands/<name>.md` and `.claude/commands/<name>.md`), so every enabled skill appears in the `/` menu of OpenCode and Claude, ready to invoke on a specific task: `/safe-editing`, `/no-hallucination`, and so on.
+Bundled: `safe-editing`, `no-hallucination`, `debug-first`, `explain-bisaya`, `clone`. Enabled skills render below the rules in every instruction file — and sync also generates a **slash command** for each one (`.opencode/commands/<name>.md` and `.claude/commands/<name>.md`), so every enabled skill appears in the `/` menu of OpenCode and Claude, ready to invoke on a specific task: `/safe-editing`, `/no-hallucination`, and so on.
 
 **Every project, instantly:** want the skills in the `/` menu of *every* project, with no per-project setup? Run `reviewer-harness global` once — it installs all bundled skills as slash commands into the global OpenCode (`~/.config/opencode/commands`) and Claude (`~/.claude/commands`) folders. From then on, they are in the `/` menu of any project you open. (Project rules still come from `sync` inside a project.)
 
+**A built-in pairing:** the `/safe-editing` command always carries the `no-hallucination` playbook inside it as a companion section — one call, both disciplines, so the AI that edits can never invent the code it edits with.
+
 ## Sub-agents and Slash Commands
 
 One master definition in the harness, generated into each runtime's format:

package/bin/cli.js

@@ -218,7 +218,7 @@ function cmdGlobal() {
   for (const { runtime, dir } of targets) {
     let written = 0, unchanged = 0, pending = 0;
     for (const skill of skills) {
-      const outcome = writeSafe(join(dir, `${skill.name}.md`), skillCommandContent(skill), dryRun);
+      const outcome = writeSafe(join(dir, `${skill.name}.md`), skillCommandContent(skill, skills), dryRun);
       if (outcome.written) written++;
       else if (outcome.dryRun && outcome.changed) pending++;
       else unchanged++;

package/lib/skills.js

@@ -147,9 +147,24 @@ export function loadSkillSections(targetDir, config) {
 // in the runtime's "/" menu (OpenCode and Claude list the files in
 // their commands folders). Invoking /<skill> hands the playbook to
 // the AI together with whatever the user types after it.
-export function skillCommandContent(skill) {
-  return (
-    `---\ndescription: ${skill.description}\n---\n\n` +
-    `${skill.body}\n\nApply this playbook to the following: $ARGUMENTS\n`
-  );
+// Companion pairings: when one of these skills is rendered as a slash
+// command, the companion's playbook is embedded in the same file —
+// so a single call always carries both disciplines. safe-editing
+// pairs with no-hallucination: the AI that edits must never invent
+// the code it edits with.
+const COMPANIONS = { "safe-editing": ["no-hallucination"] };
+
+export function skillCommandContent(skill, allSkills = []) {
+  let content =
+    `---\ndescription: ${skill.description}\n---\n\n` + `${skill.body}\n`;
+  for (const companionName of COMPANIONS[skill.name] ?? []) {
+    const companion = allSkills.find((s) => s.name === companionName);
+    if (companion) {
+      content +=
+        `\n---\n\n## Companion playbook: ${companion.name} ` +
+        `(always paired with ${skill.name})\n\n${companion.body}\n`;
+    }
+  }
+  content += `\nApply this playbook to the following: $ARGUMENTS\n`;
+  return content;
 }

package/lib/sync.js

@@ -96,7 +96,7 @@ export function sync({ targetDir, dryRun = false }) {
   if (skills.length) {
     const files = [];
     for (const skill of skills) {
-      const content = skillCommandContent(skill);
+      const content = skillCommandContent(skill, skills);
       for (const dir of [".opencode/commands", ".claude/commands"]) {
         const rel = `${dir}/${skill.name}.md`;
         files.push({ file: rel, ...writeSafe(join(targetDir, rel), content, dryRun) });

package/package.json

@@ -23,7 +23,7 @@
     "url": "https://github.com/xcell321/reviewer-harness.git"
   },
   "type": "module",
-  "version": "1.2.0",
+  "version": "1.3.0",
   "files": [
     "bin",
     "lib",

package/skills/clone.md

@@ -0,0 +1,16 @@
+---
+name: clone
+description: Fully clone a website's design — layout, components, animations, borders — while replacing all text and assets with your own.
+---
+
+## Skill: clone
+
+When to use: the user asks to clone a website or design, and gives a URL or reference to copy.
+
+- Clone the DESIGN, replace the CONTENT. That is the whole rule: everything visual may be reproduced, everything owned must be replaced.
+- First, inventory the target: sections, components, layout grid, colors, fonts, spacing, borders, and every animation (type, duration, easing, trigger). Write the inventory down before writing any code.
+- Rebuild from the inventory with original code: reproduce the look and motion, never paste the target's source code.
+- Replace every owned thing: all text (headings, skills, descriptions, projects), all image files, logos, and brand names become the user's own content or placeholders. Image placement and sizes may be copied; image files may not.
+- Front-end only: a clone reproduces the look, never the backend — no login, database, or dynamic data.
+- If the target is the user's own site, their own assets may be reused.
+- Afterwards, validate: compare screenshots side by side, check responsive breakpoints, and audit that no third-party image, text, or brand remains. Report what was cloned and what was replaced.