git-impact 0.3.0 → 0.6.3

package/dist/storage/db.test.js

@@ -0,0 +1,152 @@
+"use strict";
+var __createBinding = (this && this.__createBinding) || (Object.create ? (function(o, m, k, k2) {
+    if (k2 === undefined) k2 = k;
+    var desc = Object.getOwnPropertyDescriptor(m, k);
+    if (!desc || ("get" in desc ? !m.__esModule : desc.writable || desc.configurable)) {
+      desc = { enumerable: true, get: function() { return m[k]; } };
+    }
+    Object.defineProperty(o, k2, desc);
+}) : (function(o, m, k, k2) {
+    if (k2 === undefined) k2 = k;
+    o[k2] = m[k];
+}));
+var __setModuleDefault = (this && this.__setModuleDefault) || (Object.create ? (function(o, v) {
+    Object.defineProperty(o, "default", { enumerable: true, value: v });
+}) : function(o, v) {
+    o["default"] = v;
+});
+var __importStar = (this && this.__importStar) || (function () {
+    var ownKeys = function(o) {
+        ownKeys = Object.getOwnPropertyNames || function (o) {
+            var ar = [];
+            for (var k in o) if (Object.prototype.hasOwnProperty.call(o, k)) ar[ar.length] = k;
+            return ar;
+        };
+        return ownKeys(o);
+    };
+    return function (mod) {
+        if (mod && mod.__esModule) return mod;
+        var result = {};
+        if (mod != null) for (var k = ownKeys(mod), i = 0; i < k.length; i++) if (k[i] !== "default") __createBinding(result, mod, k[i]);
+        __setModuleDefault(result, mod);
+        return result;
+    };
+})();
+Object.defineProperty(exports, "__esModule", { value: true });
+const vitest_1 = require("vitest");
+const fs = __importStar(require("fs"));
+const os = __importStar(require("os"));
+const path = __importStar(require("path"));
+const db_1 = require("./db");
+let tmp;
+(0, vitest_1.beforeEach)(() => {
+    tmp = fs.mkdtempSync(path.join(os.tmpdir(), "git-impact-test-"));
+});
+(0, vitest_1.afterEach)(() => {
+    fs.rmSync(tmp, { recursive: true, force: true });
+});
+(0, vitest_1.describe)("context.json round-trip", () => {
+    (0, vitest_1.it)("saves and loads context", () => {
+        (0, db_1.saveContext)({
+            companyDescription: "Test Co",
+            managerPriorities: "Ship fast",
+            glossary: { RLS: "data security" },
+        }, tmp);
+        const loaded = (0, db_1.loadContext)(tmp);
+        (0, vitest_1.expect)(loaded?.companyDescription).toBe("Test Co");
+        (0, vitest_1.expect)(loaded?.glossary.RLS).toBe("data security");
+    });
+    (0, vitest_1.it)("returns null when no context file exists", () => {
+        (0, vitest_1.expect)((0, db_1.loadContext)(tmp)).toBeNull();
+    });
+    (0, vitest_1.it)("preserves privacy config", () => {
+        (0, db_1.saveContext)({
+            companyDescription: "X",
+            managerPriorities: "Y",
+            glossary: {},
+            privacy: { redact: false, filePatterns: ["*.internal"] },
+        }, tmp);
+        const loaded = (0, db_1.loadContext)(tmp);
+        (0, vitest_1.expect)(loaded?.privacy?.redact).toBe(false);
+        (0, vitest_1.expect)(loaded?.privacy?.filePatterns).toEqual(["*.internal"]);
+    });
+});
+(0, vitest_1.describe)("impact entries", () => {
+    const item = (over = {}) => ({
+        status: "done",
+        summary: "Shipped X",
+        impact: "Unblocked Y",
+        provenance: "pr",
+        ...over,
+    });
+    (0, vitest_1.it)("getLastEntryDate returns null when empty", () => {
+        (0, vitest_1.expect)((0, db_1.getLastEntryDate)(tmp)).toBeNull();
+    });
+    (0, vitest_1.it)("saves an entry and getLastEntryDate finds it", () => {
+        (0, db_1.saveEntry)({
+            date: "2026-05-09",
+            repoPath: tmp,
+            repoName: "test",
+            totalCommits: 1,
+            totalFiles: 1,
+            filesSummary: "src",
+            items: [item()],
+            rawJson: "[]",
+            createdAt: new Date().toISOString(),
+        }, tmp);
+        (0, vitest_1.expect)((0, db_1.getLastEntryDate)(tmp)).toBe("2026-05-09");
+    });
+    (0, vitest_1.it)("getLastEntryDate returns the most recent across many entries", () => {
+        const dates = ["2026-05-01", "2026-05-09", "2026-05-05"];
+        for (const date of dates) {
+            (0, db_1.saveEntry)({
+                date,
+                repoPath: tmp,
+                repoName: "r",
+                totalCommits: 1,
+                totalFiles: 1,
+                filesSummary: "",
+                items: [item()],
+                rawJson: "[]",
+                createdAt: new Date().toISOString(),
+            }, tmp);
+        }
+        (0, vitest_1.expect)((0, db_1.getLastEntryDate)(tmp)).toBe("2026-05-09");
+    });
+    (0, vitest_1.it)("preserves provenance and refs through save → get", () => {
+        (0, db_1.saveEntry)({
+            date: "2026-05-09",
+            repoPath: tmp,
+            repoName: "r",
+            totalCommits: 1,
+            totalFiles: 1,
+            filesSummary: "",
+            items: [
+                item({ provenance: "inferred", refs: ["PR #42", "ENG-1234"] }),
+            ],
+            rawJson: "[]",
+            createdAt: new Date().toISOString(),
+        }, tmp);
+        const entries = (0, db_1.getEntriesForRange)("2026-05-09", "2026-05-09", tmp);
+        (0, vitest_1.expect)(entries[0].items[0].provenance).toBe("inferred");
+        (0, vitest_1.expect)(entries[0].items[0].refs).toEqual(["PR #42", "ENG-1234"]);
+    });
+    (0, vitest_1.it)("getEntriesForDaysAgo returns recent entries", () => {
+        const today = new Date().toISOString().slice(0, 10);
+        (0, db_1.saveEntry)({
+            date: today,
+            repoPath: tmp,
+            repoName: "r",
+            totalCommits: 1,
+            totalFiles: 1,
+            filesSummary: "",
+            items: [item()],
+            rawJson: "[]",
+            createdAt: new Date().toISOString(),
+        }, tmp);
+        const entries = (0, db_1.getEntriesForDaysAgo)(7, tmp);
+        (0, vitest_1.expect)(entries).toHaveLength(1);
+        (0, vitest_1.expect)(entries[0].date).toBe(today);
+    });
+});
+//# sourceMappingURL=db.test.js.map

package/dist/storage/db.test.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"db.test.js","sourceRoot":"","sources":["../../src/storage/db.test.ts"],"names":[],"mappings":";;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;AAAA,mCAAqE;AACrE,uCAAyB;AACzB,uCAAyB;AACzB,2CAA6B;AAC7B,6BAQc;AAEd,IAAI,GAAW,CAAC;AAEhB,IAAA,mBAAU,EAAC,GAAG,EAAE;IACd,GAAG,GAAG,EAAE,CAAC,WAAW,CAAC,IAAI,CAAC,IAAI,CAAC,EAAE,CAAC,MAAM,EAAE,EAAE,kBAAkB,CAAC,CAAC,CAAC;AACnE,CAAC,CAAC,CAAC;AAEH,IAAA,kBAAS,EAAC,GAAG,EAAE;IACb,EAAE,CAAC,MAAM,CAAC,GAAG,EAAE,EAAE,SAAS,EAAE,IAAI,EAAE,KAAK,EAAE,IAAI,EAAE,CAAC,CAAC;AACnD,CAAC,CAAC,CAAC;AAEH,IAAA,iBAAQ,EAAC,yBAAyB,EAAE,GAAG,EAAE;IACvC,IAAA,WAAE,EAAC,yBAAyB,EAAE,GAAG,EAAE;QACjC,IAAA,gBAAW,EACT;YACE,kBAAkB,EAAE,SAAS;YAC7B,iBAAiB,EAAE,WAAW;YAC9B,QAAQ,EAAE,EAAE,GAAG,EAAE,eAAe,EAAE;SACnC,EACD,GAAG,CACJ,CAAC;QACF,MAAM,MAAM,GAAG,IAAA,gBAAW,EAAC,GAAG,CAAC,CAAC;QAChC,IAAA,eAAM,EAAC,MAAM,EAAE,kBAAkB,CAAC,CAAC,IAAI,CAAC,SAAS,CAAC,CAAC;QACnD,IAAA,eAAM,EAAC,MAAM,EAAE,QAAQ,CAAC,GAAG,CAAC,CAAC,IAAI,CAAC,eAAe,CAAC,CAAC;IACrD,CAAC,CAAC,CAAC;IAEH,IAAA,WAAE,EAAC,0CAA0C,EAAE,GAAG,EAAE;QAClD,IAAA,eAAM,EAAC,IAAA,gBAAW,EAAC,GAAG,CAAC,CAAC,CAAC,QAAQ,EAAE,CAAC;IACtC,CAAC,CAAC,CAAC;IAEH,IAAA,WAAE,EAAC,0BAA0B,EAAE,GAAG,EAAE;QAClC,IAAA,gBAAW,EACT;YACE,kBAAkB,EAAE,GAAG;YACvB,iBAAiB,EAAE,GAAG;YACtB,QAAQ,EAAE,EAAE;YACZ,OAAO,EAAE,EAAE,MAAM,EAAE,KAAK,EAAE,YAAY,EAAE,CAAC,YAAY,CAAC,EAAE;SACzD,EACD,GAAG,CACJ,CAAC;QACF,MAAM,MAAM,GAAG,IAAA,gBAAW,EAAC,GAAG,CAAC,CAAC;QAChC,IAAA,eAAM,EAAC,MAAM,EAAE,OAAO,EAAE,MAAM,CAAC,CAAC,IAAI,CAAC,KAAK,CAAC,CAAC;QAC5C,IAAA,eAAM,EAAC,MAAM,EAAE,OAAO,EAAE,YAAY,CAAC,CAAC,OAAO,CAAC,CAAC,YAAY,CAAC,CAAC,CAAC;IAChE,CAAC,CAAC,CAAC;AACL,CAAC,CAAC,CAAC;AAEH,IAAA,iBAAQ,EAAC,gBAAgB,EAAE,GAAG,EAAE;IAC9B,MAAM,IAAI,GAAG,CAAC,OAA4B,EAAE,EAAc,EAAE,CAAC,CAAC;QAC5D,MAAM,EAAE,MAAM;QACd,OAAO,EAAE,WAAW;QACpB,MAAM,EAAE,aAAa;QACrB,UAAU,EAAE,IAAI;QAChB,GAAG,IAAI;KACR,CAAC,CAAC;IAEH,IAAA,WAAE,EAAC,0CAA0C,EAAE,GAAG,EAAE;QAClD,IAAA,eAAM,EAAC,IAAA,qBAAgB,EAAC,GAAG,CAAC,CAAC,CAAC,QAAQ,EAAE,CAAC;IAC3C,CAAC,CAAC,CAAC;IAEH,IAAA,WAAE,EAAC,8CAA8C,EAAE,GAAG,EAAE;QACtD,IAAA,cAAS,EACP;YACE,IAAI,EAAE,YAAY;YAClB,QAAQ,EAAE,GAAG;YACb,QAAQ,EAAE,MAAM;YAChB,YAAY,EAAE,CAAC;YACf,UAAU,EAAE,CAAC;YACb,YAAY,EAAE,KAAK;YACnB,KAAK,EAAE,CAAC,IAAI,EAAE,CAAC;YACf,OAAO,EAAE,IAAI;YACb,SAAS,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;SACpC,EACD,GAAG,CACJ,CAAC;QACF,IAAA,eAAM,EAAC,IAAA,qBAAgB,EAAC,GAAG,CAAC,CAAC,CAAC,IAAI,CAAC,YAAY,CAAC,CAAC;IACnD,CAAC,CAAC,CAAC;IAEH,IAAA,WAAE,EAAC,8DAA8D,EAAE,GAAG,EAAE;QACtE,MAAM,KAAK,GAAG,CAAC,YAAY,EAAE,YAAY,EAAE,YAAY,CAAC,CAAC;QACzD,KAAK,MAAM,IAAI,IAAI,KAAK,EAAE,CAAC;YACzB,IAAA,cAAS,EACP;gBACE,IAAI;gBACJ,QAAQ,EAAE,GAAG;gBACb,QAAQ,EAAE,GAAG;gBACb,YAAY,EAAE,CAAC;gBACf,UAAU,EAAE,CAAC;gBACb,YAAY,EAAE,EAAE;gBAChB,KAAK,EAAE,CAAC,IAAI,EAAE,CAAC;gBACf,OAAO,EAAE,IAAI;gBACb,SAAS,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;aACpC,EACD,GAAG,CACJ,CAAC;QACJ,CAAC;QACD,IAAA,eAAM,EAAC,IAAA,qBAAgB,EAAC,GAAG,CAAC,CAAC,CAAC,IAAI,CAAC,YAAY,CAAC,CAAC;IACnD,CAAC,CAAC,CAAC;IAEH,IAAA,WAAE,EAAC,kDAAkD,EAAE,GAAG,EAAE;QAC1D,IAAA,cAAS,EACP;YACE,IAAI,EAAE,YAAY;YAClB,QAAQ,EAAE,GAAG;YACb,QAAQ,EAAE,GAAG;YACb,YAAY,EAAE,CAAC;YACf,UAAU,EAAE,CAAC;YACb,YAAY,EAAE,EAAE;YAChB,KAAK,EAAE;gBACL,IAAI,CAAC,EAAE,UAAU,EAAE,UAAU,EAAE,IAAI,EAAE,CAAC,QAAQ,EAAE,UAAU,CAAC,EAAE,CAAC;aAC/D;YACD,OAAO,EAAE,IAAI;YACb,SAAS,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;SACpC,EACD,GAAG,CACJ,CAAC;QACF,MAAM,OAAO,GAAG,IAAA,uBAAkB,EAAC,YAAY,EAAE,YAAY,EAAE,GAAG,CAAC,CAAC;QACpE,IAAA,eAAM,EAAC,OAAO,CAAC,CAAC,CAAC,CAAC,KAAK,CAAC,CAAC,CAAC,CAAC,UAAU,CAAC,CAAC,IAAI,CAAC,UAAU,CAAC,CAAC;QACxD,IAAA,eAAM,EAAC,OAAO,CAAC,CAAC,CAAC,CAAC,KAAK,CAAC,CAAC,CAAC,CAAC,IAAI,CAAC,CAAC,OAAO,CAAC,CAAC,QAAQ,EAAE,UAAU,CAAC,CAAC,CAAC;IACnE,CAAC,CAAC,CAAC;IAEH,IAAA,WAAE,EAAC,6CAA6C,EAAE,GAAG,EAAE;QACrD,MAAM,KAAK,GAAG,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE,CAAC,KAAK,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC;QACpD,IAAA,cAAS,EACP;YACE,IAAI,EAAE,KAAK;YACX,QAAQ,EAAE,GAAG;YACb,QAAQ,EAAE,GAAG;YACb,YAAY,EAAE,CAAC;YACf,UAAU,EAAE,CAAC;YACb,YAAY,EAAE,EAAE;YAChB,KAAK,EAAE,CAAC,IAAI,EAAE,CAAC;YACf,OAAO,EAAE,IAAI;YACb,SAAS,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;SACpC,EACD,GAAG,CACJ,CAAC;QACF,MAAM,OAAO,GAAG,IAAA,yBAAoB,EAAC,CAAC,EAAE,GAAG,CAAC,CAAC;QAC7C,IAAA,eAAM,EAAC,OAAO,CAAC,CAAC,YAAY,CAAC,CAAC,CAAC,CAAC;QAChC,IAAA,eAAM,EAAC,OAAO,CAAC,CAAC,CAAC,CAAC,IAAI,CAAC,CAAC,IAAI,CAAC,KAAK,CAAC,CAAC;IACtC,CAAC,CAAC,CAAC;AACL,CAAC,CAAC,CAAC"}

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "git-impact",
-  "version": "0.3.0",
-  "description": "Translate your git commits into plain-English business impact",
+  "version": "0.6.3",
+  "description": "Translate your git commits into plain-English business impact — runs inside your AI editor, no API key.",
   "author": "Efraim Nafady",
   "license": "MIT",
   "repository": {
@@ -25,7 +25,9 @@
     "prepublishOnly": "npm run build",
     "dev": "ts-node src/cli/index.ts",
     "start": "node dist/cli/index.js",
-    "mcp": "node dist/mcp/server.js"
+    "mcp": "node dist/mcp/server.js",
+    "test": "vitest run",
+    "test:watch": "vitest"
   },
   "keywords": [
     "git",
@@ -38,18 +40,17 @@
   ],
   "type": "commonjs",
   "dependencies": {
-    "@anthropic-ai/sdk": "^0.95.0",
     "@modelcontextprotocol/sdk": "^1.29.0",
     "@octokit/rest": "^22.0.1",
     "better-sqlite3": "^12.9.0",
     "commander": "^14.0.3",
-    "conf": "^15.1.0",
     "simple-git": "^3.36.0"
   },
   "devDependencies": {
     "@types/better-sqlite3": "^7.6.13",
     "@types/node": "^25.6.0",
     "ts-node": "^10.9.2",
-    "typescript": "^6.0.3"
+    "typescript": "^6.0.3",
+    "vitest": "^2.1.9"
   }
 }

package/skill/SKILL.md

@@ -1,278 +1,210 @@
 ---
 name: git-impact
 description: >
-  Translates git commits into plain-English business impact bullets — ideal for
-  daily standups, manager updates, and end-of-quarter performance reviews.
-  Use this skill whenever the user says anything like: "do my standup",
-  "what did I work on today", "translate my commits", "summarize my git activity",
-  "write my standup update", "what should I say in standup", "git-impact",
-  "/git-impact", "show my impact", "translate today's work", "what did I ship",
-  "generate a performance review", "what have I done this week/month/quarter",
-  "review my commits". Also trigger for "since yesterday", "last 3 days commits",
-  or any request to turn technical git output into something a manager can read.
+  Translates git commits into plain-English business impact bullets. Use this
+  skill when the user says any of: "do my standup", "/git-impact", "what did I
+  ship today", "what did I work on", "translate my commits", "summarize my
+  git activity", "write my standup update", "what should I say in standup",
+  "show my impact", "since yesterday", "since 3d", "since last standup",
+  "what have I done this week / month / quarter", "generate a performance
+  review", "performance review prep", "review my commits", "what's blocked",
+  "weekly summary". Trigger on any request to turn raw git output into
+  something a non-technical manager can read. The skill orchestrates MCP
+  tools (get_git_activity, save_impact_entry, get_history, etc.) — it does
+  not run sqlite3 or other DB commands directly.
 ---
 
 # git-impact
 
-Translate git commits into plain-English business impact for standups, manager
-updates, and performance reviews — without an API key. You do the translation
-inline using bash to read git data and a per-repo context file for personalization.
+You translate git commits into plain-English business impact for standups,
+manager updates, and performance review prep. Your job is **orchestration**:
+call the MCP tools provided by the `git-impact` server, apply the translation
+rules, and produce the output. The MCP server owns all data access (git, DB).
+You own the language.
 
----
-
-## Sub-commands
-
-Parse the user's message to determine which mode to run:
-
-| What the user says | Mode |
-|---|---|
-| `do my standup`, `today`, `/git-impact`, no args | **today** |
-| `since yesterday`, `since 3d`, `since 2026-05-01` | **since \<when\>** |
-| `review`, `performance review`, `last 30 days`, `Q2 review` | **review** |
-| `init`, `set up context`, `configure for this repo` | **init** |
+If the `git-impact` MCP server is not available in this conversation, fall
+back to the bash steps in `references/fallback-bash.md` — but the MCP path
+is preferred everywhere it works.
 
 ---
 
-## Step 1 — Find the repo root
+## Pick a mode from the user's message
 
-Run this to find the git root from wherever you are:
-
-```bash
-git rev-parse --show-toplevel 2>/dev/null
-```
+| User says | Mode |
+|---|---|
+| "do my standup", "today", "/git-impact", no args | **standup** (default) |
+| "since yesterday", "since 3d", "since 2026-05-01" | **standup** with explicit `since_iso` |
+| "review", "performance review", "last 90 days", "Q2 review" | **review** |
+| "init", "set up context", "configure for this repo" | **init** |
+| "make a presentation", "make a slide", "make me a shareable" | **standup** + **bespoke HTML** (extra step) |
 
-If it fails, tell the user: *"No git repository found in the current directory. Open
-a project folder first, or `cd` into a repo."* Stop there.
+The default standup writes to the rolling HTML dashboard at
+`.git-impact/result.html` (regenerated by the report renderer the user
+opens with `git-impact view`). The per-day bespoke HTML is only created
+when the user explicitly asks for a presentation — don't write one by
+default; it's expensive and most days don't need it.
 
-Store the result as `REPO_ROOT`.
+If the message is ambiguous, default to **standup**.
 
 ---
 
-## Step 2 — Load context (if it exists)
+## Mode: standup
 
-```bash
-cat "$REPO_ROOT/.git-impact/context.json" 2>/dev/null || echo "NONE"
-```
+### 1. Resolve the lookback window
 
-If the file exists, parse it. It looks like:
+- If the user said an explicit "since X", convert to an ISO timestamp and use it.
+- Otherwise call **`get_last_standup_date`**. If it returns a date, use the
+  start of the day after that date as `since_iso`. If it returns null,
+  default to start-of-today.
 
-```json
-{
-  "companyDescription": "B2B SaaS for workforce analytics",
-  "managerPriorities": "Shipping on time, not breaking prod",
-  "glossary": {
-    "RLS": "data security layer",
-    "TabPFN": "AI predictions",
-    "MFA": "login security"
-  }
-}
-```
+This is the "since last standup" default — it survives weekends and days off.
 
-Use this to personalise your translation — apply the glossary and frame impact
-around what the manager cares about. If the file doesn't exist, use general
-technical language and suggest running `init` at the end.
-
----
-
-## Mode: today / since \<when\>
-
-### Fetch commits
-
-For **today**:
-```bash
-git -C "$REPO_ROOT" log \
-  --since="$(date '+%Y-%m-%d') 00:00:00" \
-  --format="%h|%s|%b|%an|%ad" \
-  --date=short \
-  HEAD
-```
+### 2. Fetch git activity
 
-For **since \<when\>** — convert the user's input to a git `--since` value:
-- `yesterday` → `--since="yesterday 00:00:00"`
-- `3d` → `--since="3 days ago 00:00:00"`
-- `2026-05-01` → `--since="2026-05-01 00:00:00"`
+Call **`get_git_activity`** with `since_iso` and (optionally) `until_iso`.
+You'll get back commits, file stats, branch, and `_repo_root` — the
+absolute path the MCP server resolved.
 
-### Fetch files changed
+> **CRITICAL: capture `_repo_root` from this response and pass it as
+> `repo_path` to every subsequent tool call** (`save_impact_entry`,
+> `render_dashboard`, `get_history`). The MCP server caches it after
+> the first successful call, but threading it explicitly is the safe
+> belt-and-suspenders move and removes any chance the second tool call
+> resolves to a different directory.
 
-```bash
-FIRST=$(git -C "$REPO_ROOT" log --since="..." --format="%h" HEAD | tail -1)
-git -C "$REPO_ROOT" diff --stat "$FIRST"^ HEAD 2>/dev/null || \
-  git -C "$REPO_ROOT" show --stat "$FIRST" 2>/dev/null
-```
+If there are no commits in the window: tell the user clearly and stop. Do
+NOT save an empty entry.
 
-### Translate
+### 3. Optional: enrich with GitHub PR data
 
-If there are no commits, say so clearly and stop.
+If the user has a `github_token` saved in their context (the
+`get_git_activity` response or a prior `get_github_activity` call will tell
+you), call **`get_github_activity`** to pull PR titles and descriptions.
+PR descriptions are the single best source for accurate "why it matters"
+text — strongly prefer them over inference.
 
-Otherwise translate into **2–5 bullet points**. Follow these rules:
+### 4. Translate
 
-1. **What + why, not what + how.** Each bullet must say what was accomplished
-   AND why it matters to the business. "Fixed a bug in the auth middleware" is
-   useless to a manager. "Fixed login failures for admin users — unblocks the
-   Q2 portal launch" is useful.
+Read **`references/translation-rules.md`** for the prompt-engineering details.
+Key rules at a glance:
 
-2. **Apply the glossary.** Replace every technical term listed in context.json
-   with its plain-English equivalent. If no glossary, infer from context.
+- **What + why**, not what + how
+- **Apply the glossary** from `context.json` (returned by the context resource
+  or visible in `get_git_activity` output)
+- **Provenance is mandatory** — every saved bullet gets `pr` / `commit_body` /
+  `commit_message` / `ticket` / `inferred`
+- **Group related commits** into one bullet, not many
+- **2-5 bullets total**, never more
 
-3. **Never hallucinate impact.** If you can't infer the business reason, say
-   "technical foundation work for [area]" rather than inventing an outcome.
+### 5. Print the user-facing output
 
-4. **Group related commits.** Three commits all touching auth tell one story —
-   write one bullet, not three.
+```
+📅 [Day, Date or date range]
 
-5. **WIP / draft commits** get `⏳ In progress:` and state what the expected
-   outcome is, not what was done so far.
+✅ [Summary]
+   → [Why it matters]
 
-6. **Be specific.** "Improved performance" is vague. "Reduced login latency
-   by ~40%" is specific. Use whatever numbers exist in the commit messages.
+⏳ In progress: [What]
+   → [Expected outcome]
 
-### Output format
+🚫 Blocked: [What]   (only if applicable)
+   → [What's needed]
 
+📁 [N] files across [areas]
+   [N] commit(s) on [branch]
 ```
-📅 [Day, Date]
 
-✅ [Plain-English summary of what was accomplished]
-   → [Why it matters — who it unblocks, what risk it reduces, what it enables]
+### 6. Save to history
 
-⏳ In progress: [What is being worked on]
-   → [Expected outcome when complete]
+Call **`save_impact_entry`** with the structured items including
+`provenance` for each. The MCP tool handles the SQLite write — never run
+`sqlite3` directly. Required fields per item: `status`, `summary`,
+`provenance`. Recommended: `impact`, `refs`.
 
-📁 [N] files changed across [brief description of areas touched]
-   [N] commit(s) on [branch name]
+Example item:
+```json
+{
+  "status": "done",
+  "summary": "Shipped multi-tenant data isolation",
+  "impact": "Unblocks SOC2 sign-off, prevents cross-company data leaks",
+  "provenance": "pr",
+  "refs": ["PR #142", "ENG-1234"]
+}
 ```
 
-### Save to history
-
-After printing the output, silently save to `.git-impact/history.db`:
-
-```bash
-mkdir -p "$REPO_ROOT/.git-impact"
-grep -qxF '.git-impact/history.db' "$REPO_ROOT/.gitignore" 2>/dev/null || \
-  printf '\n# git-impact local history (private, per-machine)\n.git-impact/history.db\n' \
-  >> "$REPO_ROOT/.gitignore"
-
-sqlite3 "$REPO_ROOT/.git-impact/history.db" "
-CREATE TABLE IF NOT EXISTS impact_entries (
-  id            INTEGER PRIMARY KEY AUTOINCREMENT,
-  date          TEXT NOT NULL,
-  repo_name     TEXT NOT NULL,
-  total_commits INTEGER NOT NULL DEFAULT 0,
-  total_files   INTEGER NOT NULL DEFAULT 0,
-  items_json    TEXT NOT NULL DEFAULT '[]',
-  created_at    TEXT NOT NULL DEFAULT (datetime('now'))
-);
-INSERT INTO impact_entries (date, repo_name, total_commits, total_files, items_json)
-VALUES ('$(date +%Y-%m-%d)', '$(basename $REPO_ROOT)', $COMMIT_COUNT, $FILE_COUNT, '$ITEMS_JSON');
-"
-```
+### 7. Regenerate the rolling dashboard, then print its URL
+
+Call **`render_dashboard`** with the same `repo_path`. It rewrites
+`.git-impact/result.html` so today's entry is included, and returns
+the `file://` URL.
 
-If `sqlite3` is not available, skip silently.
-
-### Build a polished HTML presentation
-
-After saving to history, **use your Write tool to create a bespoke HTML
-presentation** for today's standup. This is not a generic template — each day's
-file should be tailored to the actual content, with custom layout, charts, or
-diagrams when they help.
-
-**Where to write:**
-- `$REPO_ROOT/.git-impact/standups/YYYY-MM-DD.html` — today's file
-- `$REPO_ROOT/.git-impact/standups/index.html` — list of all standups (regenerate it)
-
-**Stack (all CDN, no install):**
-- Tailwind CSS via `<script src="https://cdn.tailwindcss.com">`
-- Inter font via Google Fonts
-- Chart.js (`https://cdn.jsdelivr.net/npm/chart.js`) only if there are real numbers worth charting
-- Mermaid (`https://cdn.jsdelivr.net/npm/mermaid/dist/mermaid.esm.min.mjs`) for flow/architecture diagrams when relevant
-
-**Required structure:**
-1. **Hero** — date label + a bold, plain-English headline that captures the day
-   ("Shipped safety analytics, hardened tenant isolation" — not "9 commits")
-2. **Stats grid** — 3-4 metric cards (commits, files, PRs merged, areas touched)
-3. **Achievement cards** — one per ✅ item with status pill, title, summary,
-   "→ Why it matters" line, and tags (PR #, area, file count)
-4. **Optional visual** — only when the content warrants one (a Mermaid flow
-   diagram for architecture changes, a Chart.js chart for ratios/comparisons,
-   a code-style block for a key formula). Skip if forced.
-5. **Footer** — file count, branch, link back to `index.html`
-
-**Design language:**
-- Dark theme by default (`bg-slate-950`), generous spacing, max width 4xl
-- Cards: `bg-slate-900/50 border border-slate-800 rounded-2xl p-6`
-- Status pills: emerald for done, amber for in-progress, rose for blocked
-- Print-friendly via `@media print`
-
-**Status pill colors:**
-- ✅ Shipped → `bg-emerald-500/20 text-emerald-400`
-- ⏳ In Progress → `bg-amber-500/20 text-amber-400`
-- 🚫 Blocked → `bg-rose-500/20 text-rose-400`
-
-After writing both files, print the file URL on the very last line of your reply:
+End your reply with that URL on its own last line so the user can
+⌘-click to open:
 
 ```
-🎯 file://$REPO_ROOT/.git-impact/standups/YYYY-MM-DD.html
+🎯 file:///<absolute-repo-path>/.git-impact/result.html
 ```
 
-Replace `$REPO_ROOT` with the real absolute path so the user can ⌘-click.
+Don't try to open a browser yourself — printing the URL is enough.
+
+**Only if the user explicitly asked for a "presentation", "slide",
+"shareable", or "screenshot-friendly" output**, ALSO read
+`references/html-template.md` and use your `Write` tool to create
+`<repo>/.git-impact/standups/YYYY-MM-DD.html` (plus update
+`standups/index.html`). Most days don't need this — skip by default.
 
 ---
 
 ## Mode: review
 
-Fetch saved history and synthesise a performance review.
-
-Parse the period from the user's message:
-- `last 30 days` / `30d` → last 30 days
-- `last 90 days` / `90d` → last 90 days (default)
-- `Q2-2026` → April 1 – June 30, 2026
-
-```bash
-sqlite3 "$REPO_ROOT/.git-impact/history.db" \
-  "SELECT date, repo_name, total_commits, items_json
-   FROM impact_entries
-   WHERE date >= '$FROM' AND date <= '$TO'
-   ORDER BY date ASC;" 2>/dev/null
+1. Parse the period from the user's message:
+   - "last 30 days" / "30d" → `last_days: 30`
+   - "last 90 days" / "90d" / no arg → `last_days: 90`
+   - "Q2-2026" → `from_date: 2026-04-01`, `to_date: 2026-06-30`
+2. Call **`get_history`** with the parsed window.
+3. If no entries returned: tell the user
+   *"No saved history yet for this period. Use the standup mode daily to
+   build up history, then come back."* and stop.
+4. Synthesise themes (Features, Reliability, Security, Code review,
+   Infrastructure). Only include themes that apply.
+5. Frame as **performance review prep** (evidence pack), not a finished
+   review — bullets should include dates and refs the user can paste into
+   their own writing.
+
+Output:
 ```
+Performance Review Prep — [Period]
 
-If the DB doesn't exist or returns nothing: *"No saved history found for this
-period. Use the standup mode daily to build up history, then come back."*
-
-Otherwise synthesise:
-
-```
-Performance Review — [Period]
-
-[One headline sentence — biggest contribution this period]
+[One headline sentence — biggest contribution]
 
 🚀 [High-impact theme]
-   • Specific achievement...
+   • Specific achievement [date, refs]
 
 ✅ [Medium-impact theme]
-   • Specific achievement...
+   • ...
 
 🔧 [Lower-impact theme]
    • ...
 
----
 📊 [N] commits across [N] working days
 ```
 
-Group by theme (Features shipped, Reliability, Security, Code review,
-Infrastructure). Only include themes that apply.
-
 ---
 
 ## Mode: init
 
-Ask the user three questions one at a time:
+Ask one at a time:
 
 1. *"What does your company/product do? (1–2 sentences)"*
 2. *"What does your manager care most about?"*
-3. *"Any technical terms to translate? Format: RLS=data security, MFA=login security (leave blank to skip)"*
+3. *"Technical terms to translate? Format: RLS=data security, MFA=login security (blank to skip)"*
 
-Then write `.git-impact/context.json` and tell the user:
-*"Saved to `.git-impact/context.json`. Commit this to share the glossary with
-your team. history.db is gitignored automatically."*
+Then call **`update_context`** with the answers. Tell the user:
+*"Saved to `.git-impact/context.json`. Commit this to share the glossary with your team."*
+
+If the install also wrote slash command files for other editors (Cursor,
+Copilot, Gemini), point that out so they know the same workflow works
+elsewhere.
 
 ---
 
@@ -280,6 +212,11 @@ your team. history.db is gitignored automatically."*
 
 - Write for a non-technical manager. No jargon that isn't in the glossary.
 - Short sentences. No filler. Skip "this change" / "this commit" constructions.
-- Confident — if you know the impact, state it. If not, use
-  "technical foundation work for X", never hedge with "might potentially".
+- Confident — if you know the impact, state it. If you guessed, label
+  `provenance: inferred` and use phrases like "technical foundation work
+  for X". Never hedge with "might potentially".
 - 2 accurate bullets beat 5 vague ones.
+
+For prompt details, anti-patterns, and the full output format, see
+`references/translation-rules.md`. For the bespoke daily HTML, see
+`references/html-template.md`.