gaslighting-engine 0.2.0 → 0.2.2

package/.agents/prompts/gaslighting.md

@@ -30,3 +30,5 @@ Rules:
 - If something is incomplete, declare it explicitly.
 
 Before claiming completion, perform the self-audit in `.gaslighting/GASLIGHTING.md`.
+
+To refresh this Gaslighting Codex install later, run `npx gaslighting-engine@latest upgrade`.

package/.agents/skills/gaslighting/SKILL.md

@@ -99,3 +99,11 @@ Do not produce a plan without files.
 Do not say what should be done.
 
 Generate the actual project discipline documents.
+
+## Update Rule
+
+When the user asks how to update this Gaslighting Codex install, give the simple command:
+
+```bash
+npx gaslighting-engine@latest upgrade
+```

package/.codex/prompts/gaslighting.md

@@ -30,3 +30,5 @@ Rules:
 - If something is incomplete, declare it explicitly.
 
 Before claiming completion, perform the self-audit in `.gaslighting/GASLIGHTING.md`.
+
+To refresh this Gaslighting Codex install later, run `npx gaslighting-engine@latest upgrade`.

package/.codex/skills/gaslighting/SKILL.md

@@ -99,3 +99,11 @@ Do not produce a plan without files.
 Do not say what should be done.
 
 Generate the actual project discipline documents.
+
+## Update Rule
+
+When the user asks how to update this Gaslighting Codex install, give the simple command:
+
+```bash
+npx gaslighting-engine@latest upgrade
+```

package/README.md

@@ -84,11 +84,13 @@ gaslighting init "I want to build a hospital website."
 gaslighting-engine generate "Build an ecommerce MVP."
 gaslighting-engine update "The hospital is actually an OB-GYN clinic, not dermatology."
 gaslighting-engine doctor
+gaslighting-engine upgrade
 gaslighting-engine codex-install
 gaslighting-engine codex-doctor
 gaslighting-engine skill
 gaslighting-engine agents
 gaslighting-engine care
+gaslighting-engine care --github-url https://github.com/user/repo.git
 ```
 
 ## Output Layout
@@ -113,18 +115,33 @@ This file tracks non-blocking but important care risks:
 
 These are warnings, not fake blockers. The agent should keep implementing, but it must keep warning and recording gaps until they are resolved.
 
+If GitHub is not connected yet, run:
+
+```bash
+gaslighting-engine care --github-url https://github.com/user/repo.git
+```
+
+This initializes Git when needed and connects `origin`. If `origin` already exists and must be replaced, use `--force-remote`.
+
 ## Update Notice
 
 Gaslighting-engine checks npm for a newer version when you run normal commands.
 
+The simple update command is:
+
+```bash
+npx gaslighting-engine@latest upgrade
+```
+
+This updates the Codex skill and prompt files in the current project. No `--force` is needed.
+
 If an update exists, it prints a short notice like:
 
 ```txt
 Gaslighting-engine update available:
 - current: 0.1.0
 - latest:  0.1.1
-- update:  npm install -g gaslighting-engine@latest
-- npx:     npx gaslighting-engine@latest
+- update:  npx gaslighting-engine@latest upgrade
 ```
 
 The update check is best-effort and never blocks the command. Disable it with:

package/dist/cli.js

@@ -7,6 +7,7 @@ import { runGenerate } from "./commands/generate.js";
 import { runInit } from "./commands/init.js";
 import { runSkill } from "./commands/skill.js";
 import { runUpdate } from "./commands/update.js";
+import { runUpgrade } from "./commands/upgrade.js";
 import { packageVersion } from "./version.js";
 const projectTypes = [
     "hospital_homepage",
@@ -58,6 +59,8 @@ Examples:
   $ gaslighting "Build an ecommerce MVP." --type ecommerce
   $ gaslighting-engine init "Build a landing page" --dry-run
   $ gaslighting-engine doctor
+  $ gaslighting-engine care --github-url https://github.com/user/repo.git
+  $ gaslighting-engine upgrade
   $ gaslighting-engine codex-install --force
 
 Defaults:
@@ -98,7 +101,17 @@ Defaults:
         .option("--path <path>", "target directory")
         .option("--lang <lang>", "language: en or ko", "en")
         .option("--type <type>", "project type override", parseProjectType)
+        .option("--github-url <url>", "initialize git if needed and connect origin to this GitHub URL")
+        .option("--force-remote", "replace an existing origin remote when used with --github-url")
         .action(runCare);
+    program
+        .command("upgrade")
+        .description("Update the local Codex Gaslighting install with one simple command")
+        .option("--no-force", "preserve existing files and create .new variants instead")
+        .option("--dry-run", "print files without writing")
+        .option("--path <path>", "target directory")
+        .option("--scope <scope>", "project or user", "project")
+        .action(runUpgrade);
     program
         .command("codex-install")
         .description("Install Gaslighting as a Codex-optimized project or user skill")
@@ -121,7 +134,7 @@ export function normalizeDefaultInitArgv(argv) {
         return argv;
     if (args.some((arg) => ["--help", "-h", "--version", "-V"].includes(arg)))
         return argv;
-    const commands = new Set(["init", "generate", "update", "doctor", "skill", "agents", "care", "codex-install", "codex-doctor"]);
+    const commands = new Set(["init", "generate", "update", "doctor", "skill", "agents", "care", "upgrade", "codex-install", "codex-doctor"]);
     const firstMeaningful = args.find((arg) => !arg.startsWith("-"));
     if (firstMeaningful && commands.has(firstMeaningful))
         return argv;

package/dist/commands/care.js

@@ -1,5 +1,5 @@
 import { generateProjectCareDoc } from "../core/generateDocs.js";
-import { inspectProjectCare } from "../core/projectCare.js";
+import { connectGitHubRemote, inspectProjectCare } from "../core/projectCare.js";
 import { printBanner } from "../utils/banner.js";
 import { writeDocs } from "../utils/file.js";
 export function runCare(rawUserRequest = "Project care audit", options) {
@@ -13,6 +13,19 @@ export function runCare(rawUserRequest = "Project care audit", options) {
         noTodo: true,
         noShortcut: true,
     };
+    if (options.githubUrl && !options.dryRun) {
+        printBanner("GITHUB CARE");
+        console.log("Git/GitHub repair:");
+        for (const result of connectGitHubRemote(root, options.githubUrl, options.forceRemote)) {
+            console.log(`${result.ok ? "PASS" : "WARN"} ${result.step}: ${result.message}`);
+        }
+        console.log("");
+    }
+    if (options.githubUrl && options.dryRun) {
+        printBanner("GITHUB CARE");
+        console.log(`Dry run: would connect GitHub remote to ${options.githubUrl}`);
+        console.log("");
+    }
     const results = writeDocs(root, generateProjectCareDoc(input, root), options.force, options.dryRun);
     const care = inspectProjectCare(root);
     printBanner("PROJECT CARE");

package/dist/commands/codexInstall.js

@@ -26,6 +26,7 @@ export function runCodexInstall(options) {
     console.log('- If Codex exposes enabled skills in slash commands, use: /gaslighting');
     console.log("- If neither appears immediately, restart Codex and reopen this project.");
     console.log("- Fallback prompt file: .gaslighting/CODEX_GASLIGHTING.md");
+    console.log("- Update later with: npx gaslighting-engine@latest upgrade");
 }
 export function runCodexDoctor(options) {
     const target = resolveTargetPath(options);
@@ -46,12 +47,12 @@ export function runCodexDoctor(options) {
     const hasSkill = checks.some((check) => check.ok && check.file.endsWith("skills/gaslighting/SKILL.md"));
     if (!hasSkill) {
         process.exitCode = 1;
-        console.log("\nNo gaslighting skill was found. Run: gaslighting codex-install --force");
+        console.log("\nNo gaslighting skill was found. Run: npx gaslighting-engine@latest upgrade");
         return;
     }
     console.log("\nCodex install looks usable. Restart Codex if the skill does not appear yet.");
 }
-function resolveTargetPath(options) {
+export function resolveTargetPath(options) {
     if (options.path)
         return resolve(options.path);
     if (options.scope === "user")

package/dist/commands/upgrade.js

@@ -0,0 +1,27 @@
+import { generateCodexInstallDocs } from "../core/generateDocs.js";
+import { printBanner } from "../utils/banner.js";
+import { writeDocs } from "../utils/file.js";
+import { packageVersion } from "../version.js";
+import { resolveTargetPath } from "./codexInstall.js";
+export function runUpgrade(options) {
+    const target = resolveTargetPath(options);
+    const force = options.force ?? true;
+    const results = writeDocs(target, generateCodexInstallDocs(), force, options.dryRun);
+    printBanner("UPGRADE");
+    console.log(`Version: ${packageVersion}`);
+    console.log(`Target: ${target}\n`);
+    console.log("Updated Codex files:");
+    for (const result of results) {
+        const suffix = result.status === "created_variant"
+            ? " (existing file preserved)"
+            : result.status === "overwritten"
+                ? " (overwritten)"
+                : result.status === "dry_run"
+                    ? " (dry run)"
+                    : "";
+        console.log(`- ${result.filename}${suffix}`);
+    }
+    console.log("\nDone.");
+    console.log("Restart Codex or reopen this project if the old skill is still visible.");
+    console.log('Use: /gaslighting, "$gaslighting", or say "Use the gaslighting skill."');
+}

package/dist/core/generateOtherMarkdown.js

@@ -424,6 +424,14 @@ Do not produce a plan without files.
 Do not say what should be done.
 
 Generate the actual project discipline documents.
+
+## Update Rule
+
+When the user asks how to update this Gaslighting Codex install, give the simple command:
+
+\`\`\`bash
+npx gaslighting-engine@latest upgrade
+\`\`\`
 `;
 }
 export function generateSkillOpenAiYaml() {
@@ -472,6 +480,12 @@ Rules:
 
 Before claiming completion, perform the self-audit in \`.gaslighting/GASLIGHTING.md\`.
 
+To refresh the Codex skill files later, run:
+
+\`\`\`bash
+npx gaslighting-engine@latest upgrade
+\`\`\`
+
 Proceed.
 `;
 }
@@ -508,6 +522,8 @@ Rules:
 - If something is incomplete, declare it explicitly.
 
 Before claiming completion, perform the self-audit in \`.gaslighting/GASLIGHTING.md\`.
+
+To refresh this Gaslighting Codex install later, run \`npx gaslighting-engine@latest upgrade\`.
 `;
 }
 export function generateSkillReferenceDocs() {

package/dist/core/projectCare.js

@@ -2,6 +2,57 @@ import { execFileSync } from "node:child_process";
 import { existsSync } from "node:fs";
 import { join } from "node:path";
 import { decisionDate, projectPurpose } from "./content.js";
+export function connectGitHubRemote(root, githubUrl, forceRemote = false) {
+    const results = [];
+    const normalizedUrl = githubUrl.trim();
+    if (!normalizedUrl) {
+        return [{ step: "GitHub URL", ok: false, message: "No GitHub URL was provided." }];
+    }
+    if (!/github\.com[:/]/i.test(normalizedUrl)) {
+        return [{ step: "GitHub URL", ok: false, message: "The provided URL does not look like a GitHub remote URL." }];
+    }
+    if (runGit(root, ["rev-parse", "--is-inside-work-tree"]) !== "true") {
+        if (runGitCommand(root, ["init"])) {
+            results.push({ step: "git init", ok: true, message: "Initialized a Git repository." });
+        }
+        else {
+            results.push({ step: "git init", ok: false, message: "Could not initialize a Git repository. Confirm Git is installed and the directory is writable." });
+            return results;
+        }
+    }
+    else {
+        results.push({ step: "git init", ok: true, message: "Git repository already exists." });
+    }
+    const existingOrigin = runGit(root, ["remote", "get-url", "origin"]);
+    if (!existingOrigin) {
+        const added = runGitCommand(root, ["remote", "add", "origin", normalizedUrl]);
+        results.push({
+            step: "git remote add origin",
+            ok: added,
+            message: added ? `Connected origin to ${normalizedUrl}.` : "Could not add origin remote.",
+        });
+        return results;
+    }
+    if (existingOrigin === normalizedUrl) {
+        results.push({ step: "git remote", ok: true, message: `Origin already points to ${normalizedUrl}.` });
+        return results;
+    }
+    if (!forceRemote) {
+        results.push({
+            step: "git remote",
+            ok: false,
+            message: `Origin already points to ${existingOrigin}. Re-run with --force-remote to replace it.`,
+        });
+        return results;
+    }
+    const replaced = runGitCommand(root, ["remote", "set-url", "origin", normalizedUrl]);
+    results.push({
+        step: "git remote set-url origin",
+        ok: replaced,
+        message: replaced ? `Replaced origin with ${normalizedUrl}.` : "Could not replace origin remote.",
+    });
+    return results;
+}
 export function inspectProjectCare(root) {
     const isGitRepository = runGit(root, ["rev-parse", "--is-inside-work-tree"]) === "true";
     const gitBranch = isGitRepository ? runGit(root, ["branch", "--show-current"]) : undefined;
@@ -115,6 +166,7 @@ ${care.checks.map((check) => `- [${check.ok ? "x" : " "}] ${check.label}: ${chec
 - Do make a practical assumption, record it, and keep moving.
 - If Git is not initialized, ask for a GitHub URL and offer the exact commands.
 - If Git is initialized but no GitHub remote exists, ask for the remote URL and offer \`git remote add origin <url>\`.
+- If the user provides a GitHub URL, run \`gaslighting-engine care --github-url <url>\` or connect it directly with Git CLI.
 - If GitHub is connected, record the remote URL here and in \`DECISION_LOG.md\` when it changes.
 - If domain or deployment details are missing, keep warning until they are confirmed.
 - Treat missing domain, deployment, analytics, email, and privacy ownership as mission-critical launch risks, not as reasons to abandon the task.
@@ -133,3 +185,12 @@ function runGit(root, args) {
         return undefined;
     }
 }
+function runGitCommand(root, args) {
+    try {
+        execFileSync("git", args, { cwd: root, stdio: ["ignore", "ignore", "ignore"] });
+        return true;
+    }
+    catch {
+        return false;
+    }
+}

package/dist/utils/updateCheck.js

@@ -11,8 +11,7 @@ export async function notifyIfUpdateAvailable(argv) {
         console.error("Gaslighting-engine update available:");
         console.error(`- current: ${packageVersion}`);
         console.error(`- latest:  ${latestVersion}`);
-        console.error(`- update:  npm install -g ${packageName}@latest`);
-        console.error(`- npx:     npx ${packageName}@latest`);
+        console.error(`- update:  npx ${packageName}@latest upgrade`);
         console.error("");
     }
     catch {

package/dist/version.js

@@ -1,2 +1,2 @@
 export const packageName = "gaslighting-engine";
-export const packageVersion = "0.2.0";
+export const packageVersion = "0.2.2";

package/docs/codex-usage.md

@@ -38,6 +38,14 @@ Check the install:
 npx gaslighting-engine codex-doctor
 ```
 
+Update the Codex skill later:
+
+```bash
+npx gaslighting-engine@latest upgrade
+```
+
+This is the recommended update flow. It overwrites the local Codex skill and prompt files with the latest package version.
+
 ## Generate Discipline Docs
 
 Generate documents:

package/docs/examples.md

@@ -19,6 +19,7 @@ Published usage:
 
 ```bash
 npx gaslighting-engine "I want to build a hospital website."
+npx gaslighting-engine@latest upgrade
 ```
 
 This writes discipline documents under `.gaslighting/` and keeps only the Codex pointer `AGENTS.md` in the root.
@@ -27,6 +28,7 @@ Project-care refresh:
 
 ```bash
 npx gaslighting-engine care "I want to build a hospital website." --force
+npx gaslighting-engine care --github-url https://github.com/user/repo.git --force
 ```
 
 Update check test:

package/examples/ecommerce/.codex/prompts/gaslighting.md

@@ -30,3 +30,5 @@ Rules:
 - If something is incomplete, declare it explicitly.
 
 Before claiming completion, perform the self-audit in `.gaslighting/GASLIGHTING.md`.
+
+To refresh this Gaslighting Codex install later, run `npx gaslighting-engine@latest upgrade`.

package/examples/ecommerce/.codex/skills/gaslighting/SKILL.md

@@ -99,3 +99,11 @@ Do not produce a plan without files.
 Do not say what should be done.
 
 Generate the actual project discipline documents.
+
+## Update Rule
+
+When the user asks how to update this Gaslighting Codex install, give the simple command:
+
+```bash
+npx gaslighting-engine@latest upgrade
+```

package/examples/ecommerce/.gaslighting/CODEX_PROMPT.md

@@ -32,4 +32,10 @@ Rules:
 
 Before claiming completion, perform the self-audit in `.gaslighting/GASLIGHTING.md`.
 
+To refresh the Codex skill files later, run:
+
+```bash
+npx gaslighting-engine@latest upgrade
+```
+
 Proceed.

package/examples/ecommerce/.gaslighting/PROJECT_CARE.md

@@ -63,6 +63,7 @@ The agent must treat this project as mission-critical. If something can put deli
 - Do make a practical assumption, record it, and keep moving.
 - If Git is not initialized, ask for a GitHub URL and offer the exact commands.
 - If Git is initialized but no GitHub remote exists, ask for the remote URL and offer `git remote add origin <url>`.
+- If the user provides a GitHub URL, run `gaslighting-engine care --github-url <url>` or connect it directly with Git CLI.
 - If GitHub is connected, record the remote URL here and in `DECISION_LOG.md` when it changes.
 - If domain or deployment details are missing, keep warning until they are confirmed.
 - Treat missing domain, deployment, analytics, email, and privacy ownership as mission-critical launch risks, not as reasons to abandon the task.

package/examples/hospital-homepage/.codex/prompts/gaslighting.md

@@ -30,3 +30,5 @@ Rules:
 - If something is incomplete, declare it explicitly.
 
 Before claiming completion, perform the self-audit in `.gaslighting/GASLIGHTING.md`.
+
+To refresh this Gaslighting Codex install later, run `npx gaslighting-engine@latest upgrade`.

package/examples/hospital-homepage/.codex/skills/gaslighting/SKILL.md

@@ -99,3 +99,11 @@ Do not produce a plan without files.
 Do not say what should be done.
 
 Generate the actual project discipline documents.
+
+## Update Rule
+
+When the user asks how to update this Gaslighting Codex install, give the simple command:
+
+```bash
+npx gaslighting-engine@latest upgrade
+```

package/examples/hospital-homepage/.gaslighting/CODEX_PROMPT.md

@@ -32,4 +32,10 @@ Rules:
 
 Before claiming completion, perform the self-audit in `.gaslighting/GASLIGHTING.md`.
 
+To refresh the Codex skill files later, run:
+
+```bash
+npx gaslighting-engine@latest upgrade
+```
+
 Proceed.

package/examples/hospital-homepage/.gaslighting/PROJECT_CARE.md

@@ -63,6 +63,7 @@ The agent must treat this project as mission-critical. If something can put deli
 - Do make a practical assumption, record it, and keep moving.
 - If Git is not initialized, ask for a GitHub URL and offer the exact commands.
 - If Git is initialized but no GitHub remote exists, ask for the remote URL and offer `git remote add origin <url>`.
+- If the user provides a GitHub URL, run `gaslighting-engine care --github-url <url>` or connect it directly with Git CLI.
 - If GitHub is connected, record the remote URL here and in `DECISION_LOG.md` when it changes.
 - If domain or deployment details are missing, keep warning until they are confirmed.
 - Treat missing domain, deployment, analytics, email, and privacy ownership as mission-critical launch risks, not as reasons to abandon the task.

package/examples/landing-page/.codex/prompts/gaslighting.md

@@ -30,3 +30,5 @@ Rules:
 - If something is incomplete, declare it explicitly.
 
 Before claiming completion, perform the self-audit in `.gaslighting/GASLIGHTING.md`.
+
+To refresh this Gaslighting Codex install later, run `npx gaslighting-engine@latest upgrade`.

package/examples/landing-page/.codex/skills/gaslighting/SKILL.md

@@ -99,3 +99,11 @@ Do not produce a plan without files.
 Do not say what should be done.
 
 Generate the actual project discipline documents.
+
+## Update Rule
+
+When the user asks how to update this Gaslighting Codex install, give the simple command:
+
+```bash
+npx gaslighting-engine@latest upgrade
+```

package/examples/landing-page/.gaslighting/CODEX_PROMPT.md

@@ -32,4 +32,10 @@ Rules:
 
 Before claiming completion, perform the self-audit in `.gaslighting/GASLIGHTING.md`.
 
+To refresh the Codex skill files later, run:
+
+```bash
+npx gaslighting-engine@latest upgrade
+```
+
 Proceed.

package/examples/landing-page/.gaslighting/PROJECT_CARE.md

@@ -62,6 +62,7 @@ The agent must treat this project as mission-critical. If something can put deli
 - Do make a practical assumption, record it, and keep moving.
 - If Git is not initialized, ask for a GitHub URL and offer the exact commands.
 - If Git is initialized but no GitHub remote exists, ask for the remote URL and offer `git remote add origin <url>`.
+- If the user provides a GitHub URL, run `gaslighting-engine care --github-url <url>` or connect it directly with Git CLI.
 - If GitHub is connected, record the remote URL here and in `DECISION_LOG.md` when it changes.
 - If domain or deployment details are missing, keep warning until they are confirmed.
 - Treat missing domain, deployment, analytics, email, and privacy ownership as mission-critical launch risks, not as reasons to abandon the task.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "gaslighting-engine",
-  "version": "0.2.0",
+  "version": "0.2.2",
   "description": "LUDGI Gaslighting-engine: a hardcore project-discipline generator for AI coding agents.",
   "type": "module",
   "license": "MIT",