specmem-hardwicksoftware 3.5.99

package/commands/specmem-changes.md

@@ -0,0 +1,247 @@
+# SpecMem Changes - File Change History
+
+## CRITICAL: DIRECT MCP TOOL EXECUTION
+
+This command MUST directly call MCP tools - no delegation to other skills.
+
+---
+
+## INPUT VALIDATION (DO THIS FIRST!)
+
+Extract everything after `/specmem-changes`:
+
+```javascript
+const args = "$ARGUMENTS".trim();
+
+if (!args || args === "help" || args === "--help" || args === "-h") {
+  // Show HELP OUTPUT below
+  return;
+}
+
+// Parse flags
+const flags = {
+  limit: 10,
+  since: null,
+  path: null
+};
+
+// Parse --limit <N>
+const limitMatch = args.match(/--limit\s+(\d+)/);
+if (limitMatch) {
+  flags.limit = parseInt(limitMatch[1], 10);
+}
+
+// Parse --since <time>
+const sinceMatch = args.match(/--since\s+([^\s-]+(?:\s+[^\s-]+)?)/);
+if (sinceMatch) {
+  flags.since = sinceMatch[1].trim();
+}
+
+// Parse --path <pattern>
+const pathMatch = args.match(/--path\s+(\S+)/);
+if (pathMatch) {
+  flags.path = pathMatch[1];
+}
+
+// Execute with parsed flags
+```
+
+---
+
+## HELP OUTPUT
+
+Show this when no args or "help":
+
+```
+SpecMem Changes - File Change History
+
+USAGE:
+  /specmem-changes
+  /specmem-changes --since <time> --limit <N> --path <pattern>
+
+OPTIONS:
+  --limit N       Number of changes (default: 10)
+  --since TIME    Filter by time:
+                  - "today", "yesterday"
+                  - "24h", "7d", "30d"
+                  - "last week", "last month"
+                  - ISO date: "2024-01-15"
+  --path PATTERN  Filter by file path pattern
+
+EXAMPLES:
+  /specmem-changes
+  /specmem-changes --since yesterday
+  /specmem-changes --limit 20 --path src/api
+  /specmem-changes --since "last week" --path "*.ts"
+
+WHAT IT TRACKS:
+  - File additions (new files)
+  - File modifications
+  - File deletions
+  - Content changes with diffs
+
+MCP TOOL USED:
+  mcp__specmem__find_memory (with date filters and tags)
+
+RELATED:
+  /specmem-pointers  Code references
+  /specmem-code      Codebase search
+  /specmem-find      General memory search
+```
+
+---
+
+## EXECUTION
+
+**EXECUTE THIS MCP TOOL DIRECTLY:**
+
+```javascript
+mcp__specmem__find_memory({
+  query: "file change modification edit update" + (pathPattern ? " " + pathPattern : ""),
+  limit: limit || 10,
+  tags: ["file-change", "codebase"],
+  dateRange: sinceDate ? {
+    start: calculateDateFromSince(sinceDate)
+  } : undefined,
+  summarize: true,
+  maxContentLength: 200,
+  recencyBoost: true
+})
+```
+
+### Date Range Calculation
+
+Convert `--since` values to ISO 8601 format:
+
+```javascript
+function calculateDateFromSince(since) {
+  const now = new Date();
+
+  if (since === "today") {
+    const today = new Date(now);
+    today.setHours(0, 0, 0, 0);
+    return today.toISOString();
+  }
+
+  if (since === "yesterday") {
+    const yesterday = new Date(now);
+    yesterday.setDate(yesterday.getDate() - 1);
+    yesterday.setHours(0, 0, 0, 0);
+    return yesterday.toISOString();
+  }
+
+  if (since === "last week" || since === "7d") {
+    const lastWeek = new Date(now);
+    lastWeek.setDate(lastWeek.getDate() - 7);
+    return lastWeek.toISOString();
+  }
+
+  if (since === "24h") {
+    const yesterday = new Date(now);
+    yesterday.setHours(yesterday.getHours() - 24);
+    return yesterday.toISOString();
+  }
+
+  if (since === "last month" || since === "30d") {
+    const lastMonth = new Date(now);
+    lastMonth.setDate(lastMonth.getDate() - 30);
+    return lastMonth.toISOString();
+  }
+
+  // Try parsing as ISO date
+  try {
+    const date = new Date(since);
+    if (!isNaN(date.getTime())) {
+      return date.toISOString();
+    }
+  } catch (e) {
+    // Invalid date format
+  }
+
+  return null;
+}
+```
+
+### Path Filtering
+
+If `--path` provided, add to query:
+```javascript
+query: "file change modification " + pathPattern
+```
+
+---
+
+## OUTPUT FORMAT
+
+Display results as:
+
+```
+RECENT FILE CHANGES
+
+1. [<time ago>] <file path>
+   <change description preview>
+   Tags: <tags>
+
+2. [<time ago>] <file path>
+   <change description preview>
+   Tags: <tags>
+
+...
+
+Showing <N> changes. Use --limit to see more.
+```
+
+If no results:
+```
+No file changes found.
+
+Try:
+- /specmem-changes --since "last week"
+- /specmem-changes --limit 50
+- Check if file watcher is running with:
+  mcp__specmem__show_me_the_stats({})
+```
+
+---
+
+## MCP TOOL SCHEMA
+
+Tool: `mcp__specmem__find_memory`
+
+Required parameters:
+- `query`: string - Search query
+
+Optional parameters:
+- `limit`: number (1-1000, default: 10) - Max results
+- `tags`: string[] - Filter by tags
+- `dateRange`: object - Time filter
+  - `start`: string (ISO 8601) - Start date
+  - `end`: string (ISO 8601) - End date
+- `summarize`: boolean (default: true) - Return summarized content
+- `maxContentLength`: number (default: 500) - Truncate content length
+- `recencyBoost`: boolean (default: true) - Boost recent results
+- `threshold`: number (0-1, default: 0.25) - Similarity threshold
+
+---
+
+## EXAMPLES
+
+### View last 10 changes
+```
+/specmem-changes
+```
+
+### View changes from yesterday
+```
+/specmem-changes --since yesterday
+```
+
+### View 20 changes in src/ directory
+```
+/specmem-changes --limit 20 --path src/
+```
+
+### View TypeScript file changes from last week
+```
+/specmem-changes --since "last week" --path "*.ts"
+```

package/commands/specmem-code.md

@@ -0,0 +1,103 @@
+# SpecMem Code - Codebase Search (user)
+
+## REQUIRED: Check Arguments First
+
+**IF no arguments provided OR args is empty/whitespace/help/-h/--help:**
+
+OUTPUT THIS HELP AND STOP:
+
+```
+SpecMem Code - Semantic Codebase Search
+
+USAGE:
+  /specmem-code <query>           Search code by meaning
+  /specmem-code auth middleware   Find authentication middleware
+  /specmem-code --limit 20 error  Search with more results
+
+OPTIONS:
+  --limit N            Max results (default: 10, max: 100)
+  --threshold N        Min similarity score 0-1 (default: 0.1)
+  --lang LANG          Filter by language (typescript, python, go, rust, etc.)
+  --file PATTERN       Filter by file pattern (e.g., "src/**/*.ts")
+  --type TYPE          Filter by definition type (function, class, method, etc.)
+  --zoom N             Zoom level 0-100: 0=signature only, 50=balanced, 100=full (default: 50)
+  --no-memory-links    Skip linking code to related memories
+  --no-attribution     Skip user/claude attribution
+  --summarize          Truncate content for compact view
+
+EXAMPLES:
+  /specmem-code websocket handler
+  /specmem-code --limit 5 form validation
+  /specmem-code --lang python machine learning
+  /specmem-code --file "src/api/*" route handlers
+  /specmem-code --zoom 0 function signatures
+  /specmem-code --type class authentication
+
+DIFFERENCE FROM /specmem-pointers:
+  - /specmem-code: Basic code search (NO tracebacks by default)
+  - /specmem-pointers: Code search WITH tracebacks (caller/callee analysis)
+
+RELATED:
+  /specmem-pointers  Code search WITH tracebacks
+  /specmem-find      Search memories (not code)
+```
+
+**DO NOT PROCEED WITHOUT A QUERY.**
+
+---
+
+## Has Query - Execute Search
+
+**Parse the arguments:**
+- `--limit N` -> limit parameter (default: 10, max: 100)
+- `--threshold N` -> threshold parameter (default: 0.1)
+- `--lang LANG` -> language parameter
+- `--file PATTERN` -> filePattern parameter
+- `--type TYPE` -> definitionTypes parameter (array)
+- `--zoom N` -> zoom parameter (0-100, default: 50)
+- `--no-memory-links` -> includeMemoryLinks: false
+- `--no-attribution` -> includeAttribution: false
+- `--summarize` -> summarize: true
+- Remaining text = query
+
+**VALIDATION:**
+- If query is empty after parsing options -> STOP and show help
+- If limit < 1 or limit > 100 -> ERROR: "limit must be 1-100"
+- If threshold < 0 or threshold > 1 -> ERROR: "threshold must be 0-1"
+- If zoom < 0 or zoom > 100 -> ERROR: "zoom must be 0-100"
+
+**CALL THIS MCP TOOL NOW** (do not just display it, actually invoke it):
+
+Use mcp__specmem__find_code_pointers with these parameters:
+- query: the extracted search query (REQUIRED)
+- limit: parsed limit or 10
+- threshold: parsed threshold or 0.1
+- language: if --lang was provided
+- filePattern: if --file was provided
+- definitionTypes: if --type was provided (as array)
+- zoom: parsed zoom or 50
+- includeTracebacks: false (DEFAULT for /specmem-code)
+- includeMemoryLinks: true unless --no-memory-links
+- includeAttribution: false unless explicitly requested
+- summarize: true if --summarize provided
+- maxContentLength: 0 (no truncation by default)
+
+**Format the results:**
+
+```
+CODE SEARCH: "<query>"
+Found N results (threshold: X.XX)
+
+[1] <file>:<line> | <type> | score: <similarity>
+    <code snippet>
+
+    Memory Links: <related memories if available>
+
+[2] <file>:<line> | <type> | score: <similarity>
+    <code snippet>
+...
+
+TIP: Use /specmem-pointers for traceback analysis (what uses this code)
+```
+
+Show code context and memory links if available.

package/commands/specmem-configteammembercomms.md

@@ -0,0 +1,322 @@
+# SpecMem Team Member Communication Configuration
+
+Check and configure team member communication settings.
+
+## COMMAND PARSING
+
+```javascript
+const args = "$ARGUMENTS".trim();
+
+if (!args || args === "help" || args === "--help" || args === "-h") {
+  // Show HELP OUTPUT below
+  return;
+}
+
+if (args === "test") {
+  // Execute TEST action
+  return;
+}
+
+if (args === "status") {
+  // Execute STATUS action
+  return;
+}
+
+// Unknown command
+console.log("Unknown command. Use /specmem-configteammembercomms help for usage.");
+```
+
+---
+
+## INPUT VALIDATION
+
+```javascript
+const args = "$ARGUMENTS".trim();
+
+// Valid commands:
+// - /specmem-configteammembercomms          (show help)
+// - /specmem-configteammembercomms help     (show help)
+// - /specmem-configteammembercomms test     (test communication)
+// - /specmem-configteammembercomms status   (show status)
+```
+
+---
+
+## HELP OUTPUT
+
+Show this when NO args provided or "help":
+
+```
+SpecMem Team Member Communication Configuration
+
+COMMANDS:
+
+  /specmem-configteammembercomms test
+    Test team communication by sending and reading a message
+
+  /specmem-configteammembercomms status
+    Show current team status and storage backend
+
+WHAT THIS CONFIGURES:
+
+  Team members communicate via SpecMem's MCP tools:
+  - send_team_message: Send messages to team
+  - read_team_messages: Read team activity
+  - claim_task: Claim files/tasks to avoid conflicts
+  - release_task: Release claims when done
+  - get_team_status: See who's working on what
+  - broadcast_to_team: Broadcast to all team members
+  - request_help: Ask team for help
+  - respond_to_help: Answer help requests
+
+HOW IT WORKS:
+
+  All team communication goes through PostgreSQL database.
+  MCP tools handle serialization and message routing.
+  No HTTP endpoints needed - direct MCP tool calls.
+
+  Database tables:
+  - team_channels: Project-isolated channels
+  - team_messages: Messages with threading
+  - task_claims: File/task claims
+  - help_requests: Open help requests
+
+  Each project gets its own isolated schema for team data.
+
+TROUBLESHOOTING:
+
+  If communication fails:
+  1. Check SpecMem service is running
+  2. Verify PostgreSQL connection
+  3. Reload Claude session to refresh MCP
+
+RELATED COMMANDS:
+
+  /specmem-team-member status    - View team status
+  /specmem-team-member messages  - Read team messages
+  /specmem-team-member claim     - Claim a task
+
+MCP TOOLS USED:
+  - mcp__specmem__send_team_message
+  - mcp__specmem__read_team_messages
+  - mcp__specmem__get_team_status
+```
+
+---
+
+## EXECUTION
+
+### TEST Action (`/specmem-configteammembercomms test`)
+
+Test that team communication is working by:
+
+#### Step 1: Send a test message
+
+```javascript
+mcp__specmem__send_team_message({
+  message: "[CONFIG TEST] Team member communication test at " + new Date().toISOString(),
+  type: "status"
+})
+```
+
+#### Step 2: Read recent messages to verify
+
+```javascript
+mcp__specmem__read_team_messages({
+  limit: 5
+})
+```
+
+#### Step 3: Show result
+
+Check if the test message appears in the results:
+
+**SUCCESS:**
+```
+TEAM COMMUNICATION TEST
+
+✅ Send Message: OK
+✅ Read Messages: OK
+✅ Test message found in results
+
+Status: WORKING
+
+Team communication is functioning correctly.
+Database: PostgreSQL
+Storage: Project-isolated schema
+```
+
+**FAILURE:**
+```
+TEAM COMMUNICATION TEST
+
+❌ Send Message: OK
+❌ Read Messages: OK (but test message not found)
+
+Status: NOT WORKING
+
+Possible issues:
+- Database connection problem
+- Table permissions issue
+- Schema isolation misconfigured
+
+Try:
+1. Check SpecMem service is running
+2. Verify PostgreSQL connection
+3. Check logs: tail -f ~/.specmem/logs/mcp-server.log
+4. Reload Claude session
+```
+
+---
+
+### STATUS Action (`/specmem-configteammembercomms status`)
+
+Get current team status:
+
+```javascript
+mcp__specmem__get_team_status({})
+```
+
+#### Display the result:
+
+```
+TEAM COMMUNICATION STATUS
+
+Active Claims: <count>
+<list of active claims if any>
+
+Recent Activity: <count> messages in last hour
+
+Open Help Requests: <count>
+<list of help requests if any>
+
+Storage Backend: PostgreSQL
+Schema: <project schema name>
+Tables: team_channels, team_messages, task_claims, help_requests
+
+Team communication is active and operational.
+```
+
+If no activity:
+```
+TEAM COMMUNICATION STATUS
+
+Active Claims: 0
+Recent Activity: 0 messages
+
+Open Help Requests: 0
+
+Storage Backend: PostgreSQL
+Schema: <project schema name>
+
+No active team members detected.
+
+Deploy a team with:
+  /specmem-webdev <task>
+  /specmem-agents deploy <type> <task>
+```
+
+---
+
+## MCP TOOL SCHEMAS
+
+### mcp__specmem__send_team_message
+- `message`: string (required) - Message content
+- `type`: "status" | "question" | "update" | "broadcast" | "help_request" | "help_response"
+- `priority`: "low" | "normal" | "high" | "urgent"
+
+### mcp__specmem__read_team_messages
+- `limit`: number (default: 10, max: 100)
+- `unread_only`: boolean
+- `mentions_only`: boolean
+- `since`: string (ISO 8601 timestamp)
+
+### mcp__specmem__get_team_status
+No parameters required.
+
+Returns:
+- `activeClaims`: array of TaskClaim objects
+- `recentActivity`: number - Message count in last hour
+- `openHelpRequests`: array of HelpRequest objects
+
+---
+
+## MCP TOOLS USED
+
+- `mcp__specmem__send_team_message` - Send test message
+- `mcp__specmem__read_team_messages` - Read messages to verify
+- `mcp__specmem__get_team_status` - Get team status overview
+
+---
+
+## DATABASE SCHEMA INFO
+
+Team communication uses these PostgreSQL tables:
+
+### team_channels
+- Per-project channels for team communication
+- Each project gets isolated channels based on project path
+
+### team_messages
+- Messages with threading support
+- Supports @mentions and read receipts
+- Message types: status, question, update, broadcast, help_request, help_response
+
+### task_claims
+- Active file/task claims to prevent conflicts
+- Each claim has description, files, claimed_by, status
+
+### help_requests
+- Open help requests from team members
+- Status: open, answered
+- Linked to channels
+
+All tables include `project_path` for per-project isolation.
+
+---
+
+## EXAMPLES
+
+### Test team communication
+```
+/specmem-configteammembercomms test
+```
+
+Output:
+```
+TEAM COMMUNICATION TEST
+
+✅ Send Message: OK
+✅ Read Messages: OK
+✅ Test message found in results
+
+Status: WORKING
+```
+
+### Check team status
+```
+/specmem-configteammembercomms status
+```
+
+Output:
+```
+TEAM COMMUNICATION STATUS
+
+Active Claims: 2
+  - design-agent: tailwind.config.ts, src/index.css
+  - component-agent: src/components/Button.tsx
+
+Recent Activity: 15 messages in last hour
+
+Open Help Requests: 0
+
+Storage Backend: PostgreSQL
+Schema: project_specmem
+
+Team communication is active and operational.
+```
+
+### Show help
+```
+/specmem-configteammembercomms help
+```