thatgfsj-code 3.0.4 → 3.0.7

package/src/session/index.ts

@@ -1,181 +0,0 @@
-/**
- * Session Manager - Manages conversation history with auto-compaction
- */
-
-import type { ChatMessage } from '../types.js';
-import { ContextCompactor } from './compactor.js';
-
-/**
- * v2.2.4 (port from v2.1.0): patterns that, if found in an assistant
- * message, indicate the message is a truncated/aborted response that
- * should NOT be persisted into history. Without this filter, the next
- * turn's LLM sees the marker and starts echoing it back, creating a
- * self-reinforcing "[已中断]" hallucination loop.
- *
- * v2.2.6.1 tightening (smoke-test driven): the design here is a
- * two-tier check:
- *   1. STRONG markers — unambiguous pollution, always drop:
- *      - `[已中断]` bracketed (the model emits this exact form)
- *      - `[interrupted]` bracketed English equivalent
- *   2. WEAK markers — only drop if the message is also short (<200
- *      chars). Long messages mentioning "response truncated" are
- *      legitimate conversation (e.g. user complaints about past
- *      behavior), not pollution.
- *
- * Earlier drafts matched bare `已中断` substrings and "response
- * truncated" anywhere in the message — both were too greedy and
- * dropped legitimate Chinese/English conversation.
- */
-const POLLUTION_STRONG: RegExp[] = [
-  /\[已中断\]/,
-  /\[interrupted\]/i,
-];
-
-const POLLUTION_WEAK: RegExp[] = [
-  /^\s*[\*#>\-`]*\s*\[已中断\]/m,
-  /^\s*[\*#>\-`]*\s*\[interrupted\]/im,
-  /\bresponse (was )?(truncated|cut off|interrupted)\b/i,
-  /\boutput (was )?(truncated|cut off|interrupted)\b/i,
-];
-
-function looksPolluted(content: string): boolean {
-  if (!content) return false;
-  if (POLLUTION_STRONG.some(p => p.test(content))) return true;
-  // WEAK pattern gate:
-  //   - Message must be short (model got cut off mid-stream, so it
-  //     can't be long)
-  //   - Message must NOT end with '?' (questions are user complaints
-  //     about past behavior, not pollution)
-  //   - Message must NOT contain "last time" / "earlier" / "before"
-  //     (temporal references indicate user discussing past behavior)
-  if (content.length >= 200) return false;
-  if (/\?\s*$/.test(content.trim())) return false;
-  if (/\b(last time|earlier|before|previously|yesterday)\b/i.test(content)) return false;
-  if (POLLUTION_WEAK.some(p => p.test(content))) return true;
-  return false;
-}
-
-export class SessionManager {
-  private messages: ChatMessage[] = [];
-  private sessionId: string;
-  private createdAt: Date;
-  private compactor: ContextCompactor;
-  private maxMessages: number;
-  /** v2.2.4: counter for messages dropped by the pollution filter. */
-  private droppedCount: number = 0;
-  /**
-   * v3.0.0: callback invoked when the message count exceeds maxMessages.
-   * Reasonix principle: do not mutate messages to compact; instead, signal
-   * the TUI to suggest the user call /new (start a fresh session) so that
-   * the upstream prompt cache keeps a stable prefix. NWT auto-logs every
-   * meaningful event, so no history is lost — it just moves out of the
-   * live cache window.
-   */
-  public onSuggestNewSession?: (info: { currentLength: number; max: number }) => void;
-
-  constructor(maxMessages = 50, options?: { onSuggestNewSession?: SessionManager['onSuggestNewSession'] }) {
-    this.maxMessages = maxMessages;
-    this.sessionId = `session_${Date.now()}_${Math.random().toString(36).substring(2, 9)}`;
-    this.createdAt = new Date();
-    this.compactor = new ContextCompactor({ maxMessages });
-    this.onSuggestNewSession = options?.onSuggestNewSession;
-  }
-
-  addMessage(role: ChatMessage['role'], content: string, extras?: Partial<ChatMessage>): void {
-    this.messages.push({ role, content, ...extras });
-    this.autoCompact();
-  }
-
-  /**
-   * v2.2.4 (port from v2.1.0): same as addMessage but returns false
-   * (and skips the push) if the message content matches a known
-   * truncation/abort pollution pattern. Use this for assistant
-   * messages whose stream might have been aborted.
-   */
-  addMessageSafe(role: ChatMessage['role'], content: string, extras?: Partial<ChatMessage>): boolean {
-    if (role === 'assistant' && looksPolluted(content)) {
-      this.droppedCount++;
-      return false;
-    }
-    this.addMessage(role, content, extras);
-    return true;
-  }
-
-  /** v2.2.4: total messages dropped by addMessageSafe since session start. */
-  getDroppedCount(): number {
-    return this.droppedCount;
-  }
-
-  getMessages(): ChatMessage[] {
-    return [...this.messages];
-  }
-
-  getMessageCount(): number {
-    return this.messages.length;
-  }
-
-  clear(): void {
-    this.messages = [];
-  }
-
-  /**
-   * v3.0.0: "auto-compact" is now a no-op on `messages`. We instead invoke
-   * the registered `onSuggestNewSession` callback (if any) so the TUI can
-   * surface a "context is getting long, consider /new" hint. This keeps
-   * the messages array byte-stable across rounds, which is critical for
-   * prompt-cache hit-rate: any reordering or summary insertion would
-   * invalidate every cache breakpoint the upstream provider has set.
-   *
-   * Rationale (Reasonix-style): when context exceeds the model window or
-   * the configured maxMessages threshold, the right action is to start a
-   * NEW session, not to silently truncate or summarize. NWT auto-logs
-   * every meaningful event, so the user does not lose context — it just
-   * moves out of the live cache window. If the user wants a longer
-   * session, they can bump maxMessages in `~/.thatgfsj/config.json`.
-   *
-   * The original "fake compact" logic (insert `[Earlier conversation...]`
-   * summary) is preserved as `truncate()` for callers that explicitly
-   * want to compact (e.g. /new command hard-reset).
-   */
-  private autoCompact(): void {
-    if (this.messages.length <= this.maxMessages) return;
-
-    // Notify the TUI. The default TUI behavior is to render a toast:
-    //   ⚠️ 上下文超长（{currentLength}/{max}），建议调 /new 开新会话
-    //            (NWT 已自动归档历史)
-    try {
-      this.onSuggestNewSession?.({
-        currentLength: this.messages.length,
-        max: this.maxMessages,
-      });
-    } catch {
-      // Callback failure must not break the chat loop.
-    }
-    // Intentionally do NOT mutate this.messages. Prefix stability matters more.
-  }
-
-  truncate(maxMessages?: number): void {
-    if (maxMessages) {
-      this.maxMessages = maxMessages;
-      this.compactor = new ContextCompactor({ maxMessages });
-    }
-    const { compacted } = this.compactor.compact(this.messages);
-    this.messages = compacted;
-  }
-
-  getId(): string {
-    return this.sessionId;
-  }
-
-  getInfo(): { id: string; messageCount: number; createdAt: Date } {
-    return {
-      id: this.sessionId,
-      messageCount: this.messages.length,
-      createdAt: this.createdAt,
-    };
-  }
-}
-
-export { ContextCompactor } from './compactor.js';
-export type { CompactorConfig, CompressionResult } from './compactor.js';
-export * from './message.js';

package/src/session/message.ts

@@ -1,42 +0,0 @@
-/**
- * Message types and utilities
- */
-
-import type { ChatMessage, Role } from '../types.js';
-
-export { ChatMessage, Role };
-
-/**
- * Create a message
- */
-export function createMessage(role: Role, content: string, extras?: Partial<ChatMessage>): ChatMessage {
-  return { role, content, ...extras };
-}
-
-/**
- * Create a system message
- */
-export function systemMessage(content: string): ChatMessage {
-  return { role: 'system', content };
-}
-
-/**
- * Create a user message
- */
-export function userMessage(content: string): ChatMessage {
-  return { role: 'user', content };
-}
-
-/**
- * Create an assistant message
- */
-export function assistantMessage(content: string): ChatMessage {
-  return { role: 'assistant', content };
-}
-
-/**
- * Create a tool result message
- */
-export function toolMessage(content: string, toolCallId: string, name: string): ChatMessage {
-  return { role: 'tool', content, tool_call_id: toolCallId, name };
-}

package/src/skills/brainstorming.ts

@@ -1,43 +0,0 @@
-import type { Skill } from './index.js';
-
-export const brainstormingSkill: Skill = {
-  id: 'brainstorming',
-  name: 'Brainstorming',
-  description: 'Explore multiple approaches before committing to a solution',
-  category: 'planning',
-  autoActivate: ['怎么', 'how to', '方案', 'approach', '有没有', 'alternatives'],
-  prompt: `## Brainstorming Mode
-
-When exploring solutions, don't jump to the first idea. Instead:
-
-### 1. Generate Options
-List 3-5 different approaches, including at least one unconventional one.
-
-### 2. Evaluate Each
-For each approach, briefly note:
-- **Pros**: What makes it good
-- **Cons**: What could go wrong
-- **Effort**: How much work (quick/medium/heavy)
-
-### 3. Recommend
-Pick the best approach and explain WHY it's the best fit for this specific situation.
-
-### Format
-\`\`\`
-## Approaches
-
-### Option A: [Name]
-- Pros: ...
-- Cons: ...
-- Effort: medium
-
-### Option B: [Name]
-- Pros: ...
-- Cons: ...
-- Effort: quick
-
-**Recommendation**: Option B because [specific reason]
-\`\`\`
-
-Don't just list options - give a clear recommendation with reasoning.`,
-};

package/src/skills/code-review.ts

@@ -1,45 +0,0 @@
-import type { Skill } from './index.js';
-
-export const codeReviewSkill: Skill = {
-  id: 'code-review',
-  name: 'Code Review',
-  description: 'Systematic code review for quality, security, and correctness',
-  category: 'review',
-  autoActivate: ['review', '审查', '检查代码', 'code quality'],
-  prompt: `## Code Review Checklist
-
-When reviewing code (your own or others):
-
-### Correctness
-- Does it do what it's supposed to?
-- Are edge cases handled?
-- Are error cases handled?
-
-### Security
-- No hardcoded secrets or API keys
-- Input validation on user data
-- No SQL injection, XSS, or path traversal risks
-
-### Performance
-- No unnecessary loops or allocations
-- Efficient data structures
-- No N+1 queries or blocking calls
-
-### Readability
-- Clear variable/function names
-- Appropriate comments (why, not what)
-- Consistent style with codebase
-
-### Testability
-- Can this be easily tested?
-- Are dependencies injectable?
-- Are side effects isolated?
-
-### Output Format
-\`\`\`
-## Review Summary
-✅ Good: [what's done well]
-⚠️ Suggestions: [improvements]
-🔴 Issues: [must fix]
-\`\`\``,
-};

package/src/skills/executing-plans.ts

@@ -1,27 +0,0 @@
-import type { Skill } from './index.js';
-
-export const executingPlansSkill: Skill = {
-  id: 'executing-plans',
-  name: 'Executing Plans',
-  description: 'Execute multi-step plans methodically with verification',
-  category: 'planning',
-  prompt: `## Plan Execution Mode
-
-When executing a plan or multi-step task:
-
-1. **One step at a time** - Complete each step fully before moving to the next
-2. **Verify each step** - After each change, verify it works (read the file, run a test, check syntax)
-3. **Report progress** - Tell the user what you did for each step
-4. **Handle failures** - If a step fails, stop and explain. Don't silently skip.
-5. **Commit checkpoints** - After successful steps, suggest a git commit
-
-### Progress Format
-\`\`\`
-✅ Step 1: [What was done] - Verified
-✅ Step 2: [What was done] - Verified  
-⏳ Step 3: [Currently working on]
-⬜ Step 4: [Pending]
-\`\`\`
-
-If you encounter an unexpected issue, stop and ask the user how to proceed.`,
-};

package/src/skills/frontend-design.ts

@@ -1,35 +0,0 @@
-import type { Skill } from './index.js';
-
-export const frontendDesignSkill: Skill = {
-  id: 'frontend-design',
-  name: 'Frontend Design',
-  description: 'UI/UX best practices for web interfaces',
-  category: 'architecture',
-  autoActivate: ['ui', 'ux', 'frontend', 'css', 'layout', 'design', '界面', '页面'],
-  prompt: `## Frontend Design Principles
-
-### Layout
-- Use CSS Grid for 2D layouts, Flexbox for 1D
-- Mobile-first: design for small screens, enhance for larger
-- Consistent spacing: use a 4px or 8px grid system
-
-### Typography
-- Max 2-3 font sizes per page
-- Line height: 1.5 for body, 1.2 for headings
-- Max line length: 60-80 characters
-
-### Color
-- Use a limited palette (primary, secondary, accent, neutral)
-- Ensure contrast ratio ≥ 4.5:1 for text
-- Use color purposefully (not just decoration)
-
-### Components
-- Keep components small and focused
-- Extract reusable patterns early
-- Props should be explicit, not spread
-
-### Performance
-- Lazy load images and heavy components
-- Minimize bundle size
-- Use skeleton loaders for async content`,
-};

package/src/skills/git-workflow.ts

@@ -1,36 +0,0 @@
-import type { Skill } from './index.js';
-
-export const gitWorkflowSkill: Skill = {
-  id: 'git-workflow',
-  name: 'Git Workflow',
-  description: 'Clean git practices: commits, branches, PRs',
-  category: 'workflow',
-  autoActivate: ['git', 'commit', 'branch', 'merge', 'push', 'pull request'],
-  prompt: `## Git Best Practices
-
-### Commits
-- **Atomic**: One logical change per commit
-- **Message format**: \`type(scope): description\`
-  - feat: new feature
-  - fix: bug fix
-  - refactor: code restructuring
-  - docs: documentation
-  - test: adding tests
-  - chore: maintenance
-
-### Before Committing
-1. Review changes: \`git diff --staged\`
-2. Run tests
-3. Check for secrets or debug code
-
-### Branch Naming
-- \`feature/description\` - New features
-- \`fix/description\` - Bug fixes
-- \`refactor/description\` - Code improvements
-
-### Workflow
-1. Create branch from main
-2. Make changes with atomic commits
-3. Push and create PR
-4. Squash merge to main`,
-};

package/src/skills/improve-architecture.ts

@@ -1,38 +0,0 @@
-import type { Skill } from './index.js';
-
-export const improveArchitectureSkill: Skill = {
-  id: 'improve-architecture',
-  name: 'Improve Architecture',
-  description: 'Systematically improve codebase structure and quality',
-  category: 'architecture',
-  autoActivate: ['重构', 'refactor', '架构', 'architecture', 'clean', 'improve'],
-  prompt: `## Architecture Improvement Protocol
-
-When improving code structure:
-
-### 1. Assess Current State
-- Read the code and identify pain points
-- Look for: god classes, circular dependencies, tight coupling, code duplication
-
-### 2. Identify Patterns
-- **Single Responsibility**: Does each module/class do ONE thing?
-- **Dependency Direction**: Do high-level modules depend on low-level ones?
-- **Abstraction Level**: Is each layer at the right abstraction?
-
-### 3. Plan Changes
-- Start with the highest-impact, lowest-risk change
-- Each change should be independently valuable
-- Never refactor everything at once
-
-### 4. Execute Safely
-- Make one change at a time
-- Verify after each change
-- Commit frequently
-
-### Red Flags to Fix
-- Files over 300 lines
-- Functions over 50 lines
-- More than 3 levels of nesting
-- Copy-pasted code blocks
-- Circular imports`,
-};

package/src/skills/index.ts

@@ -1,136 +0,0 @@
-/**
- * Skills Registry - Built-in skills for development workflows
- * Inspired by skills.sh (obra/superpowers, mattpocock/skills, anthropics/skills)
- */
-
-export interface Skill {
-  id: string;
-  name: string;
-  description: string;
-  category: 'planning' | 'debugging' | 'testing' | 'architecture' | 'workflow' | 'browser' | 'review';
-  prompt: string;
-  autoActivate?: string[]; // Keywords that auto-activate this skill
-}
-
-// Import all skills
-import { writingPlansSkill } from './writing-plans.js';
-import { executingPlansSkill } from './executing-plans.js';
-import { systematicDebuggingSkill } from './systematic-debugging.js';
-import { brainstormingSkill } from './brainstorming.js';
-import { tddSkill } from './tdd.js';
-import { improveArchitectureSkill } from './improve-architecture.js';
-import { verificationSkill } from './verification.js';
-import { codeReviewSkill } from './code-review.js';
-import { prototypeSkill } from './prototype.js';
-import { triageSkill } from './triage.js';
-import { gitWorkflowSkill } from './git-workflow.js';
-import { subagentSkill } from './subagent.js';
-import { playwrightSkill } from './playwright.js';
-import { frontendDesignSkill } from './frontend-design.js';
-import { supabaseSkill } from './supabase.js';
-import { neuroweaveSkill } from './neuroweave.js';
-
-// All built-in skills (16 total)
-export const BUILTIN_SKILLS: Skill[] = [
-  writingPlansSkill,
-  executingPlansSkill,
-  systematicDebuggingSkill,
-  brainstormingSkill,
-  tddSkill,
-  improveArchitectureSkill,
-  verificationSkill,
-  codeReviewSkill,
-  prototypeSkill,
-  triageSkill,
-  gitWorkflowSkill,
-  subagentSkill,
-  playwrightSkill,
-  frontendDesignSkill,
-  supabaseSkill,
-  neuroweaveSkill,
-];
-
-// Skill registry
-export class SkillRegistry {
-  private skills: Map<string, Skill> = new Map();
-  private activeSkills: Set<string> = new Set();
-
-  constructor() {
-    for (const skill of BUILTIN_SKILLS) {
-      this.skills.set(skill.id, skill);
-    }
-    // Default active skills
-    this.activeSkills.add('writing-plans');
-    this.activeSkills.add('systematic-debugging');
-    this.activeSkills.add('verification');
-  }
-
-  get(id: string): Skill | undefined {
-    return this.skills.get(id);
-  }
-
-  list(): Skill[] {
-    return [...this.skills.values()];
-  }
-
-  listActive(): Skill[] {
-    return [...this.activeSkills].map(id => this.skills.get(id)!).filter(Boolean);
-  }
-
-  activate(id: string): boolean {
-    if (this.skills.has(id)) {
-      this.activeSkills.add(id);
-      return true;
-    }
-    return false;
-  }
-
-  deactivate(id: string): boolean {
-    return this.activeSkills.delete(id);
-  }
-
-  isActive(id: string): boolean {
-    return this.activeSkills.has(id);
-  }
-
-  /**
-   * Get all active skill prompts for system prompt injection
-   */
-  getActivePrompts(): string {
-    const active = this.listActive();
-    if (active.length === 0) return '';
-
-    return active.map(s => `### Skill: ${s.name}\n${s.prompt}`).join('\n\n');
-  }
-
-  /**
-   * Auto-activate skills based on user input
-   */
-  autoActivate(input: string): void {
-    const lower = input.toLowerCase();
-    for (const skill of this.skills.values()) {
-      if (skill.autoActivate?.some(kw => lower.includes(kw))) {
-        this.activeSkills.add(skill.id);
-      }
-    }
-  }
-}
-
-export {
-  writingPlansSkill,
-  executingPlansSkill,
-  systematicDebuggingSkill,
-  brainstormingSkill,
-  tddSkill,
-  improveArchitectureSkill,
-  verificationSkill,
-  codeReviewSkill,
-  prototypeSkill,
-  triageSkill,
-  gitWorkflowSkill,
-  subagentSkill,
-  playwrightSkill,
-  frontendDesignSkill,
-  supabaseSkill,
-  neuroweaveSkill,
-};

package/src/skills/neuroweave.ts

@@ -1,47 +0,0 @@
-import type { Skill } from './index.js';
-
-export const neuroweaveSkill: Skill = {
-  id: 'neuroweave',
-  name: 'NeuroWeave Timeline',
-  description: 'Project evolution memory - track decisions, changes, and milestones',
-  category: 'workflow',
-  autoActivate: ['timeline', 'history', 'what changed', 'why was', 'track'],
-  prompt: `## NeuroWeave Timeline (NWT)
-
-You have access to the NWT tool for tracking project evolution. Use it to:
-
-### When to Log Events
-- **After significant changes**: New features, refactors, bug fixes
-- **When making decisions**: Architecture choices, library selection, design patterns
-- **At milestones**: Feature complete, tests passing, deployment ready
-
-### How to Log
-\`\`\`
-nwt log
-  task: "Add user authentication"
-  summary: "Implemented JWT-based auth with login/register endpoints"
-  reason: "Need user accounts for personalized features"
-  files: "src/auth.ts, src/routes/auth.ts"
-  tags: "feature, auth, api"
-\`\`\`
-
-### Tags Convention
-- \`feature\` - New functionality
-- \`fix\` - Bug fixes
-- \`refactor\` - Code restructuring
-- \`decision\` - Architecture/design decisions
-- \`milestone\` - Project milestones
-- \`config\` - Configuration changes
-- \`docs\` - Documentation updates
-
-### Auto-log Rule
-After completing a multi-step task, automatically log it to NWT with:
-- task: What was done (imperative)
-- summary: How it was done
-- reason: Why it was done
-- files: What files changed
-- tags: Category labels
-
-### Archives
-Events older than 30 days are automatically archived. Use \`nwt story\` to see the full project narrative.`,
-};