devflow-kit 1.1.0 → 1.3.0

package/plugins/devflow-typescript/.claude-plugin/plugin.json

@@ -0,0 +1,22 @@
+{
+  "name": "devflow-typescript",
+  "description": "TypeScript language patterns - type safety, generics, utility types, type guards",
+  "author": {
+    "name": "DevFlow Contributors",
+    "email": "dean@keren.dev"
+  },
+  "version": "1.3.0",
+  "homepage": "https://github.com/dean0x/devflow",
+  "repository": "https://github.com/dean0x/devflow",
+  "license": "MIT",
+  "keywords": [
+    "typescript",
+    "types",
+    "generics",
+    "type-safety"
+  ],
+  "agents": [],
+  "skills": [
+    "typescript"
+  ]
+}

package/plugins/{devflow-core-skills → devflow-typescript}/skills/typescript/references/patterns.md

@@ -137,7 +137,7 @@ const isUndefined = (value: unknown): value is undefined =>
 const isNullish = (value: unknown): value is null | undefined =>
   value === null || value === undefined;
 
-const isFunction = (value: unknown): value is Function =>
+const isFunction = (value: unknown): value is (...args: unknown[]) => unknown =>
   typeof value === 'function';
 
 const isObject = (value: unknown): value is object =>
@@ -760,7 +760,7 @@ function debounce<T extends (...args: any[]) => any>(
   fn: T,
   delayMs: number
 ): (...args: Parameters<T>) => void {
-  let timeoutId: NodeJS.Timeout | null = null;
+  let timeoutId: ReturnType<typeof setTimeout> | null = null;
 
   return (...args: Parameters<T>) => {
     if (timeoutId) clearTimeout(timeoutId);
@@ -774,7 +774,7 @@ function throttle<T extends (...args: any[]) => any>(
   limitMs: number
 ): (...args: Parameters<T>) => void {
   let lastRun = 0;
-  let timeoutId: NodeJS.Timeout | null = null;
+  let timeoutId: ReturnType<typeof setTimeout> | null = null;
 
   return (...args: Parameters<T>) => {
     const now = Date.now();

package/scripts/hooks/{ambient-prompt.sh → ambient-prompt}

@@ -5,7 +5,7 @@
 # relevant skill loading via the ambient-router skill.
 # Zero file I/O beyond stdin — static injection only.
 
-set -euo pipefail
+set -e
 
 # jq is required to parse hook input JSON — silently no-op if missing
 if ! command -v jq &>/dev/null; then exit 0; fi
@@ -33,12 +33,12 @@ fi
 # Inject classification preamble
 PREAMBLE="AMBIENT MODE ACTIVE: Before responding, silently classify this prompt:
 Intent: BUILD | DEBUG | REVIEW | PLAN | EXPLORE | CHAT
-Depth: QUICK (no overhead) | STANDARD (load skills) | ESCALATE (suggest /command)
+Depth: QUICK (no overhead) | GUIDED (load skills) | ELEVATE (suggest /command)
 
-If STANDARD+: Read the ambient-router skill for classification details and skill selection matrix. For BUILD tasks, also load test-driven-development skill and enforce RED-GREEN-REFACTOR.
+If GUIDED+: Use the ambient-router skill already in your session context for classification details and skill selection matrix. Then Read the selected skills from ~/.claude/skills/<name>/SKILL.md and apply their patterns. For BUILD tasks, also load test-driven-development skill and enforce RED-GREEN-REFACTOR.
 
 If QUICK: Respond normally without stating classification.
-Only state classification aloud for STANDARD/ESCALATE."
+Only state classification aloud for GUIDED/ELEVATE."
 
 jq -n --arg ctx "$PREAMBLE" '{
   "hookSpecificOutput": {

package/scripts/hooks/{background-memory-update.sh → background-memory-update}

@@ -1,11 +1,11 @@
 #!/bin/bash
 
 # Background Working Memory Updater
-# Called by stop-update-memory.sh as a detached background process.
+# Called by stop-update-memory as a detached background process.
 # Resumes the parent session headlessly to update .memory/WORKING-MEMORY.md.
 # On failure: logs error, does nothing (no fallback).
 
-set -euo pipefail
+set -e
 
 CWD="$1"
 SESSION_ID="$2"
@@ -29,7 +29,7 @@ rotate_log() {
 
 # --- Stale Lock Recovery ---
 
-# Portable mtime in epoch seconds (same pattern as stop-update-memory.sh:35-39)
+# Portable mtime in epoch seconds (same pattern as stop-update-memory:35-39)
 get_mtime() {
   if stat --version &>/dev/null 2>&1; then
     stat -c %Y "$1"

package/scripts/hooks/{ensure-memory-gitignore.sh → ensure-memory-gitignore}

@@ -1,7 +1,7 @@
 #!/bin/bash
 # Ensures .memory/ exists and .gitignore entries are configured.
 # Called from stop and pre-compact hooks. Idempotent, ~1μs after first run.
-# Usage: source ensure-memory-gitignore.sh "$CWD"
+# Usage: source ensure-memory-gitignore "$CWD"
 
 _MEMORY_DIR="$1/.memory"
 

package/scripts/hooks/{pre-compact-memory.sh → pre-compact-memory}

@@ -6,7 +6,7 @@
 # has something to inject after compaction.
 # PreCompact hooks cannot block compaction — this is informational only.
 
-set -euo pipefail
+set -e
 
 # jq is required to parse hook input JSON — silently no-op if missing
 if ! command -v jq &>/dev/null; then exit 0; fi
@@ -19,7 +19,7 @@ if [ -z "$CWD" ]; then
 fi
 
 # Auto-create .memory/ and ensure .gitignore entries (idempotent after first run)
-source "$(cd "$(dirname "$0")" && pwd)/ensure-memory-gitignore.sh" "$CWD" || exit 0
+source "$(cd "$(dirname "$0")" && pwd)/ensure-memory-gitignore" "$CWD" || exit 0
 
 BACKUP_FILE="$CWD/.memory/backup.json"
 

package/scripts/hooks/run-hook

@@ -0,0 +1,23 @@
+: << 'CMDBLOCK'
+@echo off
+setlocal enabledelayedexpansion
+set "SCRIPT_DIR=%~dp0"
+set "HOOK_NAME=%~1"
+shift
+REM Try standard Git for Windows locations, then PATH
+set "BASH_EXE="
+if exist "C:\Program Files\Git\bin\bash.exe" set "BASH_EXE=C:\Program Files\Git\bin\bash.exe"
+if not defined BASH_EXE if exist "C:\Program Files (x86)\Git\bin\bash.exe" set "BASH_EXE=C:\Program Files (x86)\Git\bin\bash.exe"
+if not defined BASH_EXE (
+    where bash >nul 2>&1 && set "BASH_EXE=bash"
+)
+if defined BASH_EXE (
+    "%BASH_EXE%" "%SCRIPT_DIR%%HOOK_NAME%" %* & exit /b !errorlevel!
+)
+echo Warning: bash not found, DevFlow hooks require bash >&2
+exit /b 0
+CMDBLOCK
+SCRIPT_DIR="$(cd "$(dirname "$0")" && pwd)"
+HOOK_NAME="$1"
+shift
+exec bash "$SCRIPT_DIR/${HOOK_NAME}" "$@"

package/scripts/hooks/session-start-memory

@@ -0,0 +1,151 @@
+#!/bin/bash
+
+# SessionStart Hook
+# Injects working memory AND ambient skill content as additionalContext.
+# Memory: restores .memory/WORKING-MEMORY.md + patterns + git state + compact recovery.
+# Ambient: injects ambient-router SKILL.md so Claude has it in context (no Read call needed).
+# Either section can fire independently — ambient works even without memory files.
+
+set -e
+
+# jq is required to parse hook input JSON — silently no-op if missing
+if ! command -v jq &>/dev/null; then exit 0; fi
+
+INPUT=$(cat)
+
+CWD=$(echo "$INPUT" | jq -r '.cwd // ""' 2>/dev/null)
+if [ -z "$CWD" ]; then
+  exit 0
+fi
+
+CONTEXT=""
+
+# --- Section 1: Working Memory ---
+
+MEMORY_FILE="$CWD/.memory/WORKING-MEMORY.md"
+
+if [ -f "$MEMORY_FILE" ]; then
+  MEMORY_CONTENT=$(cat "$MEMORY_FILE")
+
+  # Read accumulated patterns if they exist
+  PATTERNS_FILE="$CWD/.memory/PROJECT-PATTERNS.md"
+  PATTERNS_CONTENT=""
+  if [ -f "$PATTERNS_FILE" ]; then
+    PATTERNS_CONTENT=$(cat "$PATTERNS_FILE")
+  fi
+
+  # Compute staleness warning
+  if stat --version &>/dev/null 2>&1; then
+    FILE_MTIME=$(stat -c %Y "$MEMORY_FILE")
+  else
+    FILE_MTIME=$(stat -f %m "$MEMORY_FILE")
+  fi
+  NOW=$(date +%s)
+  AGE=$(( NOW - FILE_MTIME ))
+
+  # Check for pre-compact memory snapshot (compaction recovery)
+  BACKUP_FILE="$CWD/.memory/backup.json"
+  COMPACT_NOTE=""
+  if [ -f "$BACKUP_FILE" ]; then
+    BACKUP_MEMORY=$(jq -r '.memory_snapshot // ""' "$BACKUP_FILE" 2>/dev/null)
+    if [ -n "$BACKUP_MEMORY" ]; then
+      BACKUP_TS=$(jq -r '.timestamp // ""' "$BACKUP_FILE" 2>/dev/null)
+      BACKUP_EPOCH=0
+      if [ -n "$BACKUP_TS" ]; then
+        BACKUP_EPOCH=$(date -j -f "%Y-%m-%dT%H:%M:%SZ" "$BACKUP_TS" +%s 2>/dev/null \
+          || date -d "$BACKUP_TS" +%s 2>/dev/null \
+          || echo "0")
+      fi
+      if [ "$BACKUP_EPOCH" -gt "$FILE_MTIME" ]; then
+        COMPACT_NOTE="
+--- PRE-COMPACT SNAPSHOT ($BACKUP_TS) ---
+Context was compacted. This snapshot may contain decisions or progress not yet in working memory.
+
+$BACKUP_MEMORY
+"
+      fi
+    fi
+  fi
+
+  STALE_WARNING=""
+  if [ "$AGE" -gt 3600 ]; then
+    HOURS=$(( AGE / 3600 ))
+    STALE_WARNING="⚠ This working memory is ${HOURS}h old. Verify before relying on it.
+
+"
+  fi
+
+  # Capture fresh git state
+  GIT_BRANCH=""
+  GIT_STATUS=""
+  GIT_LOG=""
+
+  if cd "$CWD" 2>/dev/null && git rev-parse --git-dir >/dev/null 2>&1; then
+    GIT_BRANCH=$(git branch --show-current 2>/dev/null || echo "unknown")
+    GIT_STATUS=$(git status --porcelain 2>/dev/null | head -20)
+    GIT_LOG=$(git log --oneline -5 2>/dev/null || echo "")
+  fi
+
+  # Build memory context
+  CONTEXT="${STALE_WARNING}--- WORKING MEMORY (from previous session) ---
+
+${MEMORY_CONTENT}"
+
+  # Insert accumulated patterns between working memory and git state
+  if [ -n "$PATTERNS_CONTENT" ]; then
+    CONTEXT="${CONTEXT}
+
+--- PROJECT PATTERNS (accumulated) ---
+
+${PATTERNS_CONTENT}"
+  fi
+
+  CONTEXT="${CONTEXT}
+
+--- CURRENT GIT STATE ---
+Branch: ${GIT_BRANCH}
+Recent commits:
+${GIT_LOG}"
+
+  if [ -n "$GIT_STATUS" ]; then
+    CONTEXT="${CONTEXT}
+Uncommitted changes:
+${GIT_STATUS}"
+  fi
+
+  if [ -n "$COMPACT_NOTE" ]; then
+    CONTEXT="${CONTEXT}
+${COMPACT_NOTE}"
+  fi
+fi
+
+# --- Section 2: Ambient Skill Injection ---
+
+# Inject ambient-router SKILL.md directly into context so Claude doesn't need a Read call.
+# Only injects when ambient mode is enabled (UserPromptSubmit hook present in settings).
+AMBIENT_SKILL_PATH="$HOME/.claude/skills/ambient-router/SKILL.md"
+[ ! -f "$AMBIENT_SKILL_PATH" ] && AMBIENT_SKILL_PATH="$CWD/.claude/skills/ambient-router/SKILL.md"
+
+SETTINGS_FILE="$HOME/.claude/settings.json"
+if [ -f "$AMBIENT_SKILL_PATH" ] && [ -f "$SETTINGS_FILE" ] && grep -q "ambient-prompt" "$SETTINGS_FILE" 2>/dev/null; then
+  AMBIENT_SKILL_CONTENT=$(cat "$AMBIENT_SKILL_PATH")
+  CONTEXT="${CONTEXT}
+
+--- AMBIENT ROUTER (auto-loaded) ---
+${AMBIENT_SKILL_CONTENT}"
+fi
+
+# --- Output ---
+
+# Only output if we have something to inject
+if [ -z "$CONTEXT" ]; then
+  exit 0
+fi
+
+# Output as additionalContext JSON envelope (Claude sees it as system context, not user-visible)
+jq -n --arg ctx "$CONTEXT" '{
+  "hookSpecificOutput": {
+    "hookEventName": "SessionStart",
+    "additionalContext": $ctx
+  }
+}'

package/scripts/hooks/{stop-update-memory.sh → stop-update-memory}

@@ -5,10 +5,10 @@
 # The session ends immediately — no visible edit in the TUI.
 # On failure: does nothing (stale memory is better than fake data).
 
-set -euo pipefail
+set -e
 
 # Break feedback loop: background updater's headless session triggers stop hook on exit.
-# DEVFLOW_BG_UPDATER is set by background-memory-update.sh before invoking claude.
+# DEVFLOW_BG_UPDATER is set by background-memory-update before invoking claude.
 if [ "${DEVFLOW_BG_UPDATER:-}" = "1" ]; then exit 0; fi
 
 # jq is required to parse hook input JSON — silently no-op if missing
@@ -24,7 +24,7 @@ fi
 
 # Auto-create .memory/ and ensure .gitignore entries (idempotent after first run)
 SCRIPT_DIR_EARLY="$(cd "$(dirname "$0")" && pwd)"
-source "$SCRIPT_DIR_EARLY/ensure-memory-gitignore.sh" "$CWD" || exit 0
+source "$SCRIPT_DIR_EARLY/ensure-memory-gitignore" "$CWD" || exit 0
 
 # Logging (shared log file with background updater; [stop-hook] prefix distinguishes)
 MEMORY_FILE="$CWD/.memory/WORKING-MEMORY.md"
@@ -65,7 +65,7 @@ fi
 
 # Resolve the background updater script (same directory as this hook)
 SCRIPT_DIR="$(cd "$(dirname "$0")" && pwd)"
-UPDATER="$SCRIPT_DIR/background-memory-update.sh"
+UPDATER="$SCRIPT_DIR/background-memory-update"
 if [ ! -x "$UPDATER" ]; then
   log "Skipped: updater not found/not executable at $UPDATER"
   exit 0

package/shared/agents/coder.md

@@ -2,7 +2,7 @@
 name: Coder
 description: Autonomous task implementation on feature branch. Implements, tests, and commits.
 model: inherit
-skills: core-patterns, git-safety, implementation-patterns, git-workflow, typescript, react, test-patterns, input-validation, accessibility, frontend-design
+skills: core-patterns, git-safety, implementation-patterns, git-workflow, test-patterns, input-validation
 ---
 
 # Coder Agent
@@ -33,11 +33,16 @@ You receive from orchestrator:
 
 2. **Reference handoff** (if PRIOR_PHASE_SUMMARY provided): Use summary to validate your understanding of prior work, not as the sole source of truth. The actual code is authoritative.
 
-3. **Load domain skills**: Based on DOMAIN hint, apply relevant patterns:
-   - `backend`: typescript, implementation-patterns, input-validation
-   - `frontend`: react, typescript, accessibility, frontend-design
-   - `tests`: test-patterns, typescript
-   - `fullstack`: all of the above
+3. **Load domain skills**: Based on DOMAIN hint and files in scope, dynamically load relevant language/ecosystem skills by reading their SKILL.md. Only load skills that are installed:
+   - `backend` (TypeScript): Read `~/.claude/skills/typescript/SKILL.md`, `~/.claude/skills/input-validation/SKILL.md`
+   - `backend` (Go): Read `~/.claude/skills/go/SKILL.md`
+   - `backend` (Java): Read `~/.claude/skills/java/SKILL.md`
+   - `backend` (Python): Read `~/.claude/skills/python/SKILL.md`
+   - `backend` (Rust): Read `~/.claude/skills/rust/SKILL.md`
+   - `frontend`: Read `~/.claude/skills/react/SKILL.md`, `~/.claude/skills/typescript/SKILL.md`, `~/.claude/skills/accessibility/SKILL.md`, `~/.claude/skills/frontend-design/SKILL.md`
+   - `tests`: Read `~/.claude/skills/test-patterns/SKILL.md`, `~/.claude/skills/typescript/SKILL.md`
+   - `fullstack`: Combine backend + frontend skills
+   - If a Read fails (skill not installed), skip it silently and continue.
 
 4. **Implement the plan**: Work through execution steps systematically, creating and modifying files. Follow existing patterns. Type everything. Use Result types if codebase uses them.
 

package/shared/agents/reviewer.md

@@ -34,6 +34,10 @@ The orchestrator provides:
 | `react` | `~/.claude/skills/react/SKILL.md` |
 | `accessibility` | `~/.claude/skills/accessibility/SKILL.md` |
 | `frontend-design` | `~/.claude/skills/frontend-design/SKILL.md` |
+| `go` | `~/.claude/skills/go/SKILL.md` |
+| `java` | `~/.claude/skills/java/SKILL.md` |
+| `python` | `~/.claude/skills/python/SKILL.md` |
+| `rust` | `~/.claude/skills/rust/SKILL.md` |
 
 ## Responsibilities
 
@@ -117,3 +121,7 @@ Report format for `{output_path}`:
 | react | If .tsx/.jsx files changed |
 | accessibility | If .tsx/.jsx files changed |
 | frontend-design | If .tsx/.jsx/.css/.scss files changed |
+| go | If .go files changed |
+| java | If .java files changed |
+| python | If .py files changed |
+| rust | If .rs files changed |

package/shared/skills/ambient-router/SKILL.md

@@ -36,7 +36,7 @@ Determine what the user is trying to do from their prompt.
 | **EXPLORE** | "what is", "where is", "find", "show me", "explain", "how does" | "where is the config?", "explain this function" |
 | **CHAT** | greetings, meta-questions, confirmations, short responses | "thanks", "yes", "what can you do?" |
 
-**Ambiguous prompts:** Default to the lowest-overhead classification. "Update the README" → BUILD/STANDARD. Git operations like "commit this" → QUICK.
+**Ambiguous prompts:** Default to the lowest-overhead classification. "Update the README" → BUILD/GUIDED. Git operations like "commit this" → QUICK.
 
 ## Step 2: Classify Depth
 
@@ -45,16 +45,16 @@ Determine how much enforcement the prompt warrants.
 | Depth | Criteria | Action |
 |-------|----------|--------|
 | **QUICK** | CHAT intent. EXPLORE with no analytical depth ("where is X?"). Git/devops operations (commit, push, merge, branch, pr, deploy, reinstall). Single-word continuations. | Respond normally. Zero overhead. Do not state classification. |
-| **STANDARD** | BUILD/DEBUG/REVIEW/PLAN intent (any word count). EXPLORE with analytical depth ("analyze our X", "discuss how Y works"). | Read and apply 2-3 relevant skills from the selection matrix below. State classification briefly. |
-| **ESCALATE** | Multi-file architectural change, system-wide scope, > 5 files. Detailed implementation plan (100+ words with plan structure). | Respond at best effort + recommend: "This looks like it would benefit from `/implement` for full lifecycle management." |
+| **GUIDED** | BUILD/DEBUG/REVIEW/PLAN intent (any word count). EXPLORE with analytical depth ("analyze our X", "discuss how Y works"). | Read and apply 2-3 relevant skills from the selection matrix below. State classification briefly. |
+| **ELEVATE** | Multi-file architectural change, system-wide scope, > 5 files. Detailed implementation plan (100+ words with plan structure). | Respond at best effort + recommend: "This looks like it would benefit from `/implement` for full lifecycle management." |
 
-## Step 3: Select Skills (STANDARD depth only)
+## Step 3: Select Skills (GUIDED depth only)
 
 Based on classified intent, read the following skills to inform your response.
 
 | Intent | Primary Skills | Secondary (if file type matches) |
 |--------|---------------|----------------------------------|
-| **BUILD** | test-driven-development, implementation-patterns | typescript (.ts), react (.tsx/.jsx), frontend-design (CSS/UI), input-validation (forms/API), security-patterns (auth/crypto) |
+| **BUILD** | test-driven-development, implementation-patterns | typescript (.ts), react (.tsx/.jsx), go (.go), java (.java), python (.py), rust (.rs), frontend-design (CSS/UI), input-validation (forms/API), security-patterns (auth/crypto) |
 | **DEBUG** | test-patterns, core-patterns | git-safety (if git operations involved) |
 | **REVIEW** | self-review, core-patterns | test-patterns |
 | **PLAN** | implementation-patterns | core-patterns |
@@ -65,19 +65,26 @@ See `references/skill-catalog.md` for the full skill-to-intent mapping with file
 
 ## Step 4: Apply
 
+<IMPORTANT>
+When classification is GUIDED or ELEVATE, skill application is NON-NEGOTIABLE.
+Do not rationalize skipping skills. Do not respond without loading them first.
+If test-driven-development is selected, you MUST write the failing test before ANY production code.
+</IMPORTANT>
+
 - **QUICK:** Respond directly. No preamble, no classification statement.
-- **STANDARD:** State classification briefly: `Ambient: BUILD/STANDARD. Loading: test-driven-development, implementation-patterns.` Then read the selected skills and apply their patterns to your response. For BUILD intent, enforce RED-GREEN-REFACTOR from test-driven-development.
-- **ESCALATE:** Respond with your best effort, then append: `> This task spans multiple files/systems. Consider \`/implement\` for full lifecycle (exploration → planning → implementation → review).`
+- **GUIDED:** State classification briefly: `Ambient: BUILD/GUIDED. Loading: test-driven-development, implementation-patterns.` Then read the selected skills and apply their patterns. No exceptions.
+- **ELEVATE:** Respond with your best effort, then append: `> This task spans multiple files/systems. Consider \`/implement\` for full lifecycle.`
 
 ---
 
 ## Transparency Rules
 
 1. **QUICK → silent.** No classification output.
-2. **STANDARD → brief statement.** One line: intent, depth, skills loaded.
-3. **ESCALATE → recommendation.** Best-effort response + workflow nudge.
+2. **GUIDED → brief statement + full skill enforcement.** One line: intent, depth, skills loaded. Then follow every skill requirement without shortcuts.
+3. **ELEVATE → recommendation.** Best-effort response + workflow nudge.
 4. **Never lie about classification.** If uncertain, say so.
 5. **Never over-classify.** When in doubt, go one tier lower.
+6. **Never under-apply.** Rationalization is the enemy of quality. If a skill requires a step, do the step.
 
 ## Edge Cases
 

package/shared/skills/ambient-router/references/skill-catalog.md

@@ -4,7 +4,7 @@ Full mapping of DevFlow skills to ambient intents and file-type triggers. The am
 
 ## Skills Available for Ambient Loading
 
-These skills may be loaded during STANDARD-depth ambient routing.
+These skills may be loaded during GUIDED-depth ambient routing.
 
 ### BUILD Intent
 
@@ -16,6 +16,10 @@ These skills may be loaded during STANDARD-depth ambient routing.
 | react | React components in scope | `*.tsx`, `*.jsx` |
 | frontend-design | UI/styling work | `*.css`, `*.scss`, `*.tsx` with styling keywords |
 | input-validation | Forms, APIs, user input | Files with form/input/validation keywords |
+| go | Go files in scope | `*.go` |
+| java | Java files in scope | `*.java` |
+| python | Python files in scope | `*.py` |
+| rust | Rust files in scope | `*.rs` |
 | security-patterns | Auth, crypto, secrets | Files with auth/token/crypto/password keywords |
 
 ### DEBUG Intent
@@ -61,4 +65,4 @@ These skills are loaded only by explicit DevFlow commands (primarily `/code-revi
 - **Maximum 3 skills** per ambient response (primary + up to 2 secondary)
 - **Primary skills** are always loaded for the classified intent
 - **Secondary skills** are loaded only when file patterns match conversation context
-- If more than 3 skills seem relevant, this is an ESCALATE signal
+- If more than 3 skills seem relevant, this is an ELEVATE signal

package/shared/skills/architecture-patterns/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: architecture-patterns
-description: Architecture analysis patterns for code review. Detects SOLID violations, tight coupling, layering issues, and dependency direction problems. Loaded by Reviewer agent when focus=architecture.
+description: This skill should be used when reviewing code for SOLID violations, tight coupling, or layering issues.
 user-invocable: false
 allowed-tools: Read, Grep, Glob
 ---

package/shared/skills/complexity-patterns/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: complexity-patterns
-description: Complexity analysis patterns for code review. Detects high cyclomatic complexity, deep nesting, long functions, and readability issues that hinder maintainability. Loaded by Reviewer agent when focus=complexity.
+description: This skill should be used when reviewing code for high cyclomatic complexity, deep nesting, or long functions.
 user-invocable: false
 allowed-tools: Read, Grep, Glob
 ---

package/shared/skills/consistency-patterns/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: consistency-patterns
-description: Consistency analysis patterns for code review. Detects naming convention violations, pattern deviations, unnecessary simplification, and feature truncation in diffs. Loaded by Reviewer agent when focus=consistency.
+description: This skill should be used when reviewing code for naming convention violations, pattern deviations, or inconsistent API styles.
 user-invocable: false
 allowed-tools: Read, Grep, Glob
 ---

package/shared/skills/database-patterns/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: database-patterns
-description: Database analysis patterns for code review. Detects missing indexes, slow queries, unsafe migrations, schema design issues, and connection pool misuse. Loaded by Reviewer agent when focus=database.
+description: This skill should be used when reviewing database queries, migrations, indexes, or schema changes.
 user-invocable: false
 allowed-tools: Read, Grep, Glob
 ---

package/shared/skills/dependencies-patterns/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: dependencies-patterns
-description: Dependency analysis patterns for code review. Detects known CVEs, outdated packages, license incompatibilities, and unnecessary transitive dependencies. Loaded by Reviewer agent when focus=dependencies.
+description: This skill should be used when reviewing dependency changes, lock files, or package additions.
 user-invocable: false
 allowed-tools: Read, Grep, Glob
 ---

package/shared/skills/documentation-patterns/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: documentation-patterns
-description: Documentation analysis patterns for code review. Detects doc drift from code changes, missing documentation for public APIs, stale comments, and misleading README sections. Loaded by Reviewer agent when focus=documentation.
+description: This skill should be used when reviewing for documentation drift, missing API docs, or stale comments.
 user-invocable: false
 allowed-tools: Read, Grep, Glob
 ---