@relipa/ai-flow-kit 0.0.6 → 0.0.7-beta.1

package/scripts/use.js

@@ -20,6 +20,9 @@ module.exports = async function use(target, options = {}) {
         return;
     }
 
+    // ── GitNexus index notification (all AI tools see this) ──────
+    await checkGitNexusIndexStatus();
+
     // ── Manual entry ──
     if (options.manual) {
         return await manualContext();
@@ -456,7 +459,8 @@ async function manualContext(prefillId = '') {
             { name: '✨ Feature', value: 'feature' },
             { name: '🔍 Investigation', value: 'investigation' },
             { name: '♻️  Refactor', value: 'refactor' },
-            { name: '📊 Impact Analysis', value: 'impact-analysis' }
+            { name: '📊 Impact Analysis', value: 'impact-analysis' },
+            { name: '📖 Documentation', value: 'documentation' }
         ],
         default: existing.taskType || undefined
     });
@@ -501,10 +505,25 @@ async function loadFromFile(filePath, options = {}) {
         context = JSON.parse(raw);
     } catch (_) {
         console.log(chalk.gray('  File is not JSON — auto-detecting task info from content...'));
-        context = buildContextFromPlainText(raw);
+        context = buildContextFromPlainText(raw, filePath);
     }
 
     context.mode = options.full ? 'full' : 'fast';
+
+    // Prompt for task type
+    context.taskType = await select({
+        message: 'Task type:',
+        choices: [
+            { name: '🐛 Bug Fix', value: 'bug-fix' },
+            { name: '✨ Feature', value: 'feature' },
+            { name: '🔍 Investigation', value: 'investigation' },
+            { name: '♻️  Refactor', value: 'refactor' },
+            { name: '📊 Impact Analysis', value: 'impact-analysis' },
+            { name: '📖 Documentation', value: 'documentation' }
+        ],
+        default: context.taskType || 'feature'
+    });
+
     await saveContext(context, options.save);
     printContextSummary(context);
     await suggestNextStep();
@@ -514,14 +533,29 @@ async function loadFromFile(filePath, options = {}) {
  * Build a minimal context object from arbitrary plain-text file content.
  * Tries to detect ticket ID (e.g. PROJ-33, APP-123) and a title from the first non-blank line.
  */
-function buildContextFromPlainText(text) {
+function buildContextFromPlainText(text, filePath = '') {
     // Detect ticket ID: first PROJ-123 style token anywhere in the text
     const idMatch = text.match(/\b([A-Z][A-Z0-9_]+-\d+)\b/);
-    const taskId = idMatch ? idMatch[1] : `TASK-${Date.now()}`;
 
-    // Title: first non-blank, non-id line (or first line of text)
+    let taskId;
+    if (idMatch) {
+        taskId = idMatch[1];
+    } else {
+        const fileNameOnly = filePath ? path.basename(filePath, path.extname(filePath)) : '';
+        const cleanWords = fileNameOnly.replace(/[^a-zA-Z0-9]/g, ' ')
+                                      .split(/\s+/)
+                                      .filter(Boolean)
+                                      .slice(0, 5)
+                                      .join('-')
+                                      .toUpperCase();
+        const prefix = cleanWords ? `TASK-${cleanWords}-` : 'TASK-';
+        taskId = `${prefix}${Date.now()}`;
+    }
+
+    // Title: use full filename if available, otherwise first non-blank line
+    const fullFileName = filePath ? path.basename(filePath) : '';
     const lines = text.split(/\r?\n/).map(l => l.trim()).filter(Boolean);
-    const titleLine = lines.find(l => l.length > 3) || taskId;
+    const titleLine = fullFileName || lines.find(l => l.length > 3) || taskId;
     const title = titleLine.substring(0, 120);
 
     // Task type detection from text
@@ -692,6 +726,44 @@ function printContextSummary(context) {
     console.log();
 }
 
+// ── GitNexus index status notification ───────────────────────────
+// Called at the top of use() so ALL AI tools (Claude/Gemini/Cursor/Copilot)
+// see the notification when developer runs `aiflow use TICKET`.
+const GITNEXUS_STALE_MS = 3 * 60 * 60 * 1000; // 3 hours — if still "running" after this, process died
+
+async function checkGitNexusIndexStatus() {
+    const statusPath = path.join(AIFLOW_DIR, 'gitnexus-status.json');
+    try {
+        if (!(await fs.pathExists(statusPath))) return;
+        const gn = await fs.readJson(statusPath);
+        if (gn.notified) return;
+
+        // Detect stale "running" — process was killed without updating status
+        if (gn.status === 'running' && gn.startedAt) {
+            const age = Date.now() - new Date(gn.startedAt).getTime();
+            if (age > GITNEXUS_STALE_MS) {
+                gn.status = 'error';
+                gn.error = 'timed out — process may have been killed or ran out of memory';
+                gn.notified = false;
+                await fs.writeJson(statusPath, gn, { spaces: 2 });
+            }
+        }
+
+        if (gn.status === 'done') {
+            console.log(chalk.green('✓ GitNexus indexing complete — code intelligence tools are ready.'));
+            gn.notified = true;
+            await fs.writeJson(statusPath, gn, { spaces: 2 });
+        } else if (gn.status === 'error') {
+            const detail = gn.error ? ` (${gn.error})` : gn.exitCode ? ` (exit ${gn.exitCode})` : '';
+            console.log(chalk.red(`✗ GitNexus indexing failed${detail}.`));
+            // console.log(chalk.gray('  Retry: aiflow init --with-gitnexus'));
+            gn.notified = true;
+            await fs.writeJson(statusPath, gn, { spaces: 2 });
+        }
+        // status === 'running' and not yet stale: still in progress, stay silent
+    } catch (_) {}
+}
+
 async function suggestNextStep() {
     let aiTools = ['claude']; // Default
     try {

package/upstream/.claude-plugin/marketplace.json

@@ -2,8 +2,8 @@
   "name": "superpowers-dev",
   "description": "Development marketplace for Superpowers core skills library",
   "owner": {
-    "name": "Jesse Vincent",
-    "email": "jesse@fsck.com"
+    "name": "Example Team",
+    "email": "dev@example.com"
   },
   "plugins": [
     {
@@ -12,8 +12,8 @@
       "version": "5.0.7",
       "source": "./",
       "author": {
-        "name": "Jesse Vincent",
-        "email": "jesse@fsck.com"
+        "name": "Example Developer",
+        "email": "dev@example.com"
       }
     }
   ]

package/upstream/.claude-plugin/plugin.json

@@ -3,11 +3,9 @@
   "description": "Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques",
   "version": "5.0.7",
   "author": {
-    "name": "Jesse Vincent",
-    "email": "jesse@fsck.com"
+    "name": "Example Developer",
+    "email": "dev@example.com"
   },
-  "homepage": "https://github.com/obra/superpowers",
-  "repository": "https://github.com/obra/superpowers",
   "license": "MIT",
   "keywords": [
     "skills",

package/upstream/.cursor-plugin/plugin.json

@@ -4,11 +4,9 @@
   "description": "Core skills library: TDD, debugging, collaboration patterns, and proven techniques",
   "version": "5.0.7",
   "author": {
-    "name": "Jesse Vincent",
-    "email": "jesse@fsck.com"
+    "name": "Example Developer",
+    "email": "dev@example.com"
   },
-  "homepage": "https://github.com/obra/superpowers",
-  "repository": "https://github.com/obra/superpowers",
   "license": "MIT",
   "keywords": [
     "skills",

package/upstream/docs/plans/2025-11-22-opencode-support-design.md

@@ -1,7 +1,7 @@
 # OpenCode Support Design
 
 **Date:** 2025-11-22
-**Author:** Bot & Jesse
+**Author:** Bot & developer
 **Status:** Design Complete, Awaiting Implementation
 
 ## Overview

package/upstream/docs/plans/2025-11-28-skills-improvements-from-user-feedback.md

@@ -640,7 +640,7 @@ How do we know these improvements work?
 
 1. **Configuration verification:**
    - Zero instances of "test passed but wrong config was used"
-   - Jesse doesn't say "that's not actually testing what you think"
+   - developer doesn't say "that's not actually testing what you think"
 
 2. **Process hygiene:**
    - Zero instances of "test hit wrong server"
@@ -699,7 +699,7 @@ How do we know these improvements work?
 - testing-anti-patterns: Mock-interface drift
 - requesting-code-review: Explicit file reading
 
-**Test Phase 2 with Jesse before finalizing:**
+**Test Phase 2 with developer before finalizing:**
 - Get feedback on self-reflection impact
 - Validate process hygiene approach
 - Confirm skills reading requirement is worth overhead

package/upstream/docs/testing.md

@@ -149,8 +149,8 @@ python3 tests/claude-code/analyze-token-usage.py ~/.claude/projects/<project-dir
 Session transcripts are stored in `~/.claude/projects/` with the working directory path encoded:
 
 ```bash
-# Example for /Users/jesse/Documents/GitHub/superpowers/superpowers
-SESSION_DIR="$HOME/.claude/projects/-Users-jesse-Documents-GitHub-superpowers-superpowers"
+# Example for /Users/example-user/Documents/GitHub/superpowers/superpowers
+SESSION_DIR="$HOME/.claude/projects/-Users-example-user-Documents-GitHub-superpowers-superpowers"
 
 # Find recent sessions
 ls -lt "$SESSION_DIR"/*.jsonl | head -5

package/upstream/skills/subagent-driven-development/SKILL.md

@@ -48,7 +48,7 @@ digraph process {
         "Dispatch implementer subagent (./implementer-prompt.md)" [shape=box];
         "Implementer subagent asks questions?" [shape=diamond];
         "Answer questions, provide context" [shape=box];
-        "Implementer subagent implements, tests, commits, self-reviews" [shape=box];
+        "Implementer subagent implements, tests, self-reviews" [shape=box];
         "Dispatch spec reviewer subagent (./spec-reviewer-prompt.md)" [shape=box];
         "Spec reviewer subagent confirms code matches spec?" [shape=diamond];
         "Implementer subagent fixes spec gaps" [shape=box];
@@ -63,12 +63,11 @@ digraph process {
     "Dispatch final code reviewer subagent for entire implementation" [shape=box];
     "Use superpowers:finishing-a-development-branch" [shape=box style=filled fillcolor=lightgreen];
 
-    "Read plan, extract all tasks with full text, note context, create TodoWrite" -> "Dispatch implementer subagent (./implementer-prompt.md)";
     "Dispatch implementer subagent (./implementer-prompt.md)" -> "Implementer subagent asks questions?";
     "Implementer subagent asks questions?" -> "Answer questions, provide context" [label="yes"];
     "Answer questions, provide context" -> "Dispatch implementer subagent (./implementer-prompt.md)";
-    "Implementer subagent asks questions?" -> "Implementer subagent implements, tests, commits, self-reviews" [label="no"];
-    "Implementer subagent implements, tests, commits, self-reviews" -> "Dispatch spec reviewer subagent (./spec-reviewer-prompt.md)";
+    "Implementer subagent asks questions?" -> "Implementer subagent implements, tests, self-reviews" [label="no"];
+    "Implementer subagent implements, tests, self-reviews" -> "Dispatch spec reviewer subagent (./spec-reviewer-prompt.md)";
     "Dispatch spec reviewer subagent (./spec-reviewer-prompt.md)" -> "Spec reviewer subagent confirms code matches spec?";
     "Spec reviewer subagent confirms code matches spec?" -> "Implementer subagent fixes spec gaps" [label="no"];
     "Implementer subagent fixes spec gaps" -> "Dispatch spec reviewer subagent (./spec-reviewer-prompt.md)" [label="re-review"];
@@ -146,7 +145,7 @@ Implementer: "Got it. Implementing now..."
   - Implemented install-hook command
   - Added tests, 5/5 passing
   - Self-review: Found I missed --force flag, added it
-  - Committed
+  - Reported DONE
 
 [Dispatch spec compliance reviewer]
 Spec reviewer: ✅ Spec compliant - all requirements met, nothing extra
@@ -166,7 +165,7 @@ Implementer:
   - Added verify/repair modes
   - 8/8 tests passing
   - Self-review: All good
-  - Committed
+  - Reported DONE
 
 [Dispatch spec compliance reviewer]
 Spec reviewer: ❌ Issues:

package/upstream/skills/subagent-driven-development/implementer-prompt.md

@@ -32,9 +32,8 @@ Task tool (general-purpose):
     1. Implement exactly what the task specifies
     2. Write tests (following TDD if task says to)
     3. Verify implementation works
-    4. Commit your work
-    5. Self-review (see below)
-    6. Report back
+    4. Self-review (see below)
+    5. Report back
 
     Work from: [directory]
 

package/upstream/skills/systematic-debugging/CREATION-LOG.md

@@ -4,7 +4,7 @@ Reference example of extracting, structuring, and bulletproofing a critical skil
 
 ## Source Material
 
-Extracted debugging framework from `/Users/jesse/.claude/CLAUDE.md`:
+Extracted debugging framework from `/Users/example-user/.claude/CLAUDE.md`:
 - 4-phase systematic process (Investigation → Pattern Analysis → Hypothesis → Implementation)
 - Core mandate: ALWAYS find root cause, NEVER fix symptoms
 - Rules designed to resist time pressure and rationalization

package/upstream/skills/systematic-debugging/root-cause-tracing.md

@@ -33,7 +33,7 @@ digraph when_to_use {
 
 ### 1. Observe the Symptom
 ```
-Error: git init failed in /Users/jesse/project/packages/core
+Error: git init failed in /Users/example-user/project/packages/core
 ```
 
 ### 2. Find Immediate Cause

package/upstream/skills/tdd-lean/SKILL.md

@@ -0,0 +1,127 @@
+---
+name: tdd-lean
+description: Use for Gate 3 fast mode — Batch Red-Green-Refactor. Write all tests first, run once, implement all code, run once. Framework-agnostic.
+---
+
+# TDD Lean — Gate 3 Fast Mode
+
+## When to Use
+
+**Fast mode only.** This skill replaces `superpowers:test-driven-development` in fast mode.
+Full mode continues to use `superpowers:test-driven-development` unchanged.
+
+## The Batch Red-Green-Refactor Pattern
+
+Instead of per-test Red-Green-Refactor, batch all tests first, then implement all production code.
+
+### Phase 1 — RED BATCH
+
+Write ALL test methods for the feature in test file(s).
+Run test runner ONCE → confirm all FAIL.
+
+If any test PASSes immediately → that test is wrong. Fix it before proceeding.
+
+```
+✅ Accept: Tests: 0 passed, 8 failed (1.2s)
+❌ Stop if: any test passes immediately (test is testing wrong behavior)
+```
+
+### Phase 2 — GREEN BATCH
+
+Implement ALL production code.
+Run test runner ONCE → confirm all PASS.
+
+If tests FAIL:
+- Fix inline. DO NOT spawn a subagent.
+- Maximum 2 retry runs.
+- If still failing after 2 retries: stop and report exact error to developer.
+
+```
+✅ Accept: Tests: 8 passed (2.1s)
+❌ Stop if: tests still fail after 2 retries → report to developer
+```
+
+### Phase 3 — REFACTOR
+
+Clean up duplication or naming if needed.
+Run ONCE to confirm still PASS.
+Do NOT add behavior. Do NOT fix unrelated tests.
+
+## Test Output Discipline — CRITICAL
+
+After EVERY test run, keep ONLY the summary line in context. Discard everything else.
+
+**Keep:**
+```
+✅ Tests: 12 passed (3.2s)
+❌ Tests: 10 passed, 2 failed — UserService:45 expected "X" got "Y"
+```
+
+**Discard immediately:**
+- Full stack traces
+- Framework startup logs (Spring Boot "Started in 3.2s", Jest runner header, etc.)
+- Warning and deprecation messages
+- Individual test output blocks
+
+**Why this matters:** A single Spring Boot test run produces ~300 lines (~860 tokens). Running 16–24 times per feature = 13,000–20,000 tokens from test output alone. Batch approach = 2–3 runs total.
+
+## Checkpoint Calls
+
+At each phase milestone, call the checkpoint command with your token estimate:
+
+```bash
+aiflow checkpoint --gate 3 --step "tests-written" --tokens [estimate]
+aiflow checkpoint --gate 3 --step "code-done" --tokens [estimate]
+aiflow checkpoint --gate 3 --step "tests-pass" --tokens [estimate]
+```
+
+**Token estimate:** Count approximate characters you have generated in this gate so far ÷ 3.5
+
+## Summary.md Update
+
+After Phase 2 (GREEN BATCH), append task results to `plan/[ticket-id]/summary.md`:
+
+```markdown
+### Gate 3 — Code
+- ✅ [Task name] + tests
+- ✅ [Task name] + tests
+- ❌ [Task name] (error → fixed inline)
+```
+
+Also append token data:
+```markdown
+## Token Usage
+| Gate | Tokens (est.) | Time |
+|------|---------------|------|
+| G3   | ~[value]      | [Xm] |
+```
+(Update existing row if Gate 3 row already exists; add if not.)
+
+## Gate Transition Reminder
+
+After all tests pass and Gate 3 is complete, display:
+
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+✅ GATE 3: CODE GENERATION COMPLETE
+
+All tests pass. Ready for Gate 4 (AI Self-Review).
+
+💡 Token tip: Continue in this session OR start fresh for Gate 4:
+   1. Run: aiflow task next --ticket [ticket-id]
+   2. Open a new terminal / chat session
+   3. Run: aiflow task resume [ticket-id]
+   Gate 4 will begin with a clean context window.
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+```
+
+## Mandatory Rules
+
+- ❌ DO NOT run test suite after each individual test method
+- ❌ DO NOT use `superpowers:test-driven-development` in fast mode
+- ❌ DO NOT spawn subagents to fix failing tests
+- ❌ DO NOT keep full test output in context
+- ✅ MUST run test suite exactly: once after RED BATCH, once after GREEN BATCH
+- ✅ MUST discard test output and keep only summary line
+- ✅ MUST call `aiflow checkpoint` at each milestone
+- ✅ MUST update summary.md with task results (✅/❌) and token data

package/upstream/skills/using-git-worktrees/SKILL.md

@@ -61,10 +61,9 @@ git check-ignore -q .worktrees 2>/dev/null || git check-ignore -q worktrees 2>/d
 
 **If NOT ignored:**
 
-Per Jesse's rule "Fix broken things immediately":
+Per developer's rule "Fix broken things immediately":
 1. Add appropriate line to .gitignore
-2. Commit the change
-3. Proceed with worktree creation
+2. Proceed with worktree creation
 
 **Why critical:** Prevents accidentally committing worktree contents to repository.
 
@@ -149,7 +148,7 @@ Ready to implement <feature-name>
 | `worktrees/` exists | Use it (verify ignored) |
 | Both exist | Use `.worktrees/` |
 | Neither exists | Check CLAUDE.md → Ask user |
-| Directory not ignored | Add to .gitignore + commit |
+| Directory not ignored | Add to .gitignore |
 | Tests fail during baseline | Report failures + ask |
 | No package.json/Cargo.toml | Skip dependency install |
 
@@ -186,7 +185,7 @@ You: I'm using the using-git-worktrees skill to set up an isolated workspace.
 [Run npm install]
 [Run npm test - 47 passing]
 
-Worktree ready at /Users/jesse/myproject/.worktrees/auth
+Worktree ready at /Users/example-user/myproject/.worktrees/auth
 Tests passing (47 tests, 0 failures)
 Ready to implement auth feature
 ```

package/upstream/skills/writing-plans/SKILL.md

@@ -7,7 +7,7 @@ description: Use when you have a spec or requirements for a multi-step task, bef
 
 ## Overview
 
-Write comprehensive implementation plans assuming the engineer has zero context for our codebase and questionable taste. Document everything they need to know: which files to touch for each task, code, testing, docs they might need to check, how to test it. Give them the whole plan as bite-sized tasks. DRY. YAGNI. TDD. Frequent commits.
+Write comprehensive implementation plans assuming the engineer has zero context for our codebase and questionable taste. Document everything they need to know: which files to touch for each task, code, testing, docs they might need to check, how to test it. Give them the whole plan as bite-sized tasks. DRY. YAGNI. TDD.
 
 Assume they are a skilled developer, but know almost nothing about our toolset or problem domain. Assume they don't know good test design very well.
 
@@ -40,7 +40,6 @@ This structure informs the task decomposition. Each task should produce self-con
 - "Run it to make sure it fails" - step
 - "Implement the minimal code to make the test pass" - step
 - "Run the tests and make sure they pass" - step
-- "Commit" - step
 
 ## Plan Document Header
 
@@ -95,12 +94,7 @@ def function(input):
 Run: `pytest tests/path/test.py::test_name -v`
 Expected: PASS
 
-- [ ] **Step 5: Commit**
-
-```bash
-git add tests/path/test.py src/path/file.py
-git commit -m "feat: add specific feature"
-```
+Expected: PASS
 ````
 
 ## No Placeholders
@@ -117,7 +111,7 @@ Every step must contain the actual content an engineer needs. These are **plan f
 - Exact file paths always
 - Complete code in every step — if a step changes code, show the code
 - Exact commands with expected output
-- DRY, YAGNI, TDD, frequent commits
+- DRY, YAGNI, TDD
 
 ## Self-Review
 

package/upstream/tests/brainstorm-server/package-lock.json

@@ -0,0 +1,36 @@
+{
+  "name": "brainstorm-server-tests",
+  "version": "1.0.0",
+  "lockfileVersion": 3,
+  "requires": true,
+  "packages": {
+    "": {
+      "name": "brainstorm-server-tests",
+      "version": "1.0.0",
+      "dependencies": {
+        "ws": "^8.19.0"
+      }
+    },
+    "node_modules/ws": {
+      "version": "8.19.0",
+      "resolved": "https://registry.npmjs.org/ws/-/ws-8.19.0.tgz",
+      "integrity": "sha512-blAT2mjOEIi0ZzruJfIhb3nps74PRWTCz1IjglWEEpQl5XS/UNama6u2/rjFkDDouqr4L67ry+1aGIALViWjDg==",
+      "license": "MIT",
+      "engines": {
+        "node": ">=10.0.0"
+      },
+      "peerDependencies": {
+        "bufferutil": "^4.0.1",
+        "utf-8-validate": ">=5.0.2"
+      },
+      "peerDependenciesMeta": {
+        "bufferutil": {
+          "optional": true
+        },
+        "utf-8-validate": {
+          "optional": true
+        }
+      }
+    }
+  }
+}