@kennethsolomon/shipkit 3.12.0 → 3.13.2

package/README.md

@@ -1,5 +1,7 @@
 <div align="center">
 
+<img src="assets/shipkit-logo.png" alt="ShipKit" width="260" />
+
 # SHIPKIT
 
 **A structured, quality-gated workflow system for Claude Code.**
@@ -269,6 +271,63 @@ Use these anytime — they're not part of any workflow.
 
 ---
 
+## Code Navigation (LSP)
+
+ShipKit configures LSP (Language Server Protocol) automatically — giving Claude Code go-to-definition, find-references, hover, and diagnostics instead of plain text search.
+
+**`/sk:setup-claude`** and **`/sk:setup-optimizer`** both run an LSP Integration step that:
+- Sets `ENABLE_LSP_TOOL=1` in `~/.claude/settings.json`
+- Detects your stack and installs the appropriate language server
+
+| Stack | Language Server |
+|-------|----------------|
+| TypeScript / JavaScript | `typescript-language-server` |
+| PHP | `intelephense` |
+| Python | `pylsp` |
+| Go | `gopls` |
+| Rust | `rust-analyzer` |
+| Swift | `sourcekit-lsp` |
+
+**Rule:** Prefer LSP over `rg`/Grep for code navigation. Use `rg` only when LSP is unavailable or for arbitrary text/pattern matching.
+
+---
+
+## MCP Servers & Plugins
+
+Both `/sk:setup-claude` and `/sk:setup-optimizer` offer to install three tools that enhance Claude Code's reasoning, knowledge, and session visibility. All are opt-in and idempotent.
+
+### Sequential Thinking MCP
+
+**Why it exists:** Complex problems — architecture decisions, multi-step debugging, tasks with many constraints — benefit from structured reasoning. Without it, Claude works through hard problems in a single pass, which can miss steps or lose track of constraints.
+
+**What it does:** Gives Claude a dedicated reasoning scratchpad. It thinks through steps sequentially before responding, without cluttering your conversation with the intermediate work.
+
+**Benefit:** More coherent, thorough responses on hard problems. Especially useful during `/sk:brainstorm`, `/sk:debug`, and `/sk:review`.
+
+**How it's installed:** Adds `@modelcontextprotocol/server-sequential-thinking` to `~/.mcp.json` (global, applies to all projects).
+
+### Context7
+
+**Why it exists:** Claude's training has a knowledge cutoff. When you're working with libraries that release frequently — React, Next.js, Tailwind, shadcn/ui — Claude's suggestions can reference outdated APIs, deprecated methods, or patterns that no longer apply.
+
+**What it does:** Fetches current, version-accurate documentation for libraries you're using and injects it into Claude's context at the moment it's needed.
+
+**Benefit:** Accurate code suggestions for the actual version you're running. No more `useEffect` patterns from React 17 when you're on React 19.
+
+**How it's installed:** Enables `context7@claude-plugins-official` in `~/.claude/settings.json`.
+
+### ccstatusline
+
+**Why it exists:** Knowing your context window %, active model, and current branch at a glance matters. Without it, you have to run `/sk:status` or guess when to `/compact`.
+
+**What it does:** Adds a persistent statusline to the Claude Code CLI showing context window usage, active model, git branch, and current task.
+
+**Benefit:** Always-visible session state. Know when you're approaching context limits before it becomes a problem.
+
+**How it's installed:** Runs `npx ccstatusline@latest` which writes the statusline config to `~/.claude/settings.json`.
+
+---
+
 ## All Commands
 
 <details>

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@kennethsolomon/shipkit",
-  "version": "3.12.0",
+  "version": "3.13.2",
   "description": "A structured workflow toolkit for Claude Code.",
   "keywords": [
     "claude",

package/skills/sk:setup-claude/SKILL.md

@@ -405,6 +405,63 @@ After stack detection, check and configure LSP tooling:
 
 **Idempotency:** Skip install if the server is already present. Skip settings update if `ENABLE_LSP_TOOL` is already set.
 
+### MCP Servers & Plugins
+
+After LSP setup, prompt the user to install three recommended tools that enhance Claude Code with structured reasoning, live documentation, and session visibility:
+
+> "Install recommended MCP servers & plugins? (Sequential Thinking, Context7, ccstatusline) [y/n]"
+
+If yes, install each — skip any already configured.
+
+#### 1. Sequential Thinking MCP
+
+Gives Claude a structured scratchpad for complex multi-step reasoning (architecture decisions, debugging chains, multi-constraint problems) without cluttering the conversation context.
+
+**Check:** grep `~/.mcp.json` for `sequential-thinking`. If missing, add the entry:
+
+```json
+{
+  "sequential-thinking": {
+    "command": "npx",
+    "args": ["-y", "@modelcontextprotocol/server-sequential-thinking"]
+  }
+}
+```
+
+Merge additively into `~/.mcp.json` — never overwrite existing entries. Create the file if it doesn't exist.
+
+Report: `+ sequential-thinking MCP added to ~/.mcp.json`
+
+#### 2. Context7
+
+Fetches live, version-accurate library documentation and injects it into Claude's context — eliminating stale knowledge cutoff issues when working with rapidly evolving frameworks (Tailwind 4, React 19, Next.js 15, etc.).
+
+**Check:** grep `~/.claude/settings.json` for `context7`. If missing, add to `enabledPlugins`:
+
+```json
+"enabledPlugins": {
+  "context7@claude-plugins-official": true
+}
+```
+
+Merge additively — never overwrite other `enabledPlugins` entries.
+
+Report: `+ context7 plugin enabled in ~/.claude/settings.json`
+
+#### 3. ccstatusline
+
+Configures a persistent Claude Code statusline showing context window %, active model, git branch, and current task — always visible without running `/sk:status`.
+
+**Check:** look for an existing `statusline` config in `~/.claude/settings.json`. If not already configured by ccstatusline:
+
+```bash
+npx ccstatusline@latest
+```
+
+Report: `+ ccstatusline configured`
+
+**Idempotency:** Skip each install if already present. Never overwrite existing MCP entries, plugin flags, or statusline config.
+
 ### Settings Generation (`.claude/settings.json`)
 
 Rendered from `templates/.claude/settings.json.template`. Contains:

package/skills/sk:setup-claude/templates/.claude/settings.json.template

@@ -105,7 +105,7 @@
     ],
     "PostToolUse": [
       {
-        "matcher": "Edit",
+        "matcher": "Edit|Write",
         "hooks": [
           {
             "type": "command",

package/skills/sk:setup-claude/templates/.claude/statusline.sh

@@ -26,10 +26,10 @@ fi
 # Branch
 BRANCH=$(git rev-parse --abbrev-ref HEAD 2>/dev/null || echo "none")
 
-# Task name from todo.md
+# Active task — first unchecked item in todo.md
 TASK="—"
 if [ -f "tasks/todo.md" ]; then
-    TASK=$(head -1 "tasks/todo.md" 2>/dev/null | sed 's/^# TODO.*— //' | cut -c1-40)
+    TASK=$(grep -m1 '^\- \[ \]' "tasks/todo.md" 2>/dev/null | sed 's/^- \[ \] //' | cut -c1-40)
 fi
 
 # Output single line

package/skills/sk:setup-claude/templates/hooks/session-start.sh

@@ -38,5 +38,14 @@ if [ -d "src" ]; then
     fi
 fi
 
+# Current task — first unchecked item in tasks/todo.md
+if [ -f "tasks/todo.md" ]; then
+    CURRENT_TASK=$(grep -m1 '^\- \[ \]' "tasks/todo.md" 2>/dev/null | sed 's/^- \[ \] //')
+    if [ -n "$CURRENT_TASK" ]; then
+        echo ""
+        echo "Current task: $CURRENT_TASK"
+    fi
+fi
+
 echo "==================================="
 exit 0

package/skills/sk:setup-claude/templates/hooks/validate-commit.sh

@@ -73,9 +73,10 @@ if [ -n "$STAGED" ]; then
     fi
 fi
 
-# Print warnings (non-blocking) and allow commit
+# Block commit if any violations found
 if [ -n "$WARNINGS" ]; then
-    echo -e "=== Commit Validation Warnings ===$WARNINGS\n================================" >&2
+    echo -e "=== Commit Blocked ===$WARNINGS\n\nFix the above issues before committing." >&2
+    exit 2
 fi
 
 exit 0

package/skills/sk:setup-optimizer/SKILL.md

@@ -170,6 +170,31 @@ After hooks deployment, check and configure LSP tooling:
 
 **Idempotency:** Never overwrite existing hook files — the user may have customized them. Only deploy hooks that don't exist yet. For settings.json, merge additively.
 
+### Step 1.7: MCP Servers & Plugin Check
+
+After LSP check, verify the three recommended tools are configured:
+
+1. **Sequential Thinking MCP** — grep `~/.mcp.json` for `sequential-thinking`
+2. **Context7 plugin** — grep `~/.claude/settings.json` for `context7@claude-plugins-official` in `enabledPlugins`
+3. **ccstatusline** — check `~/.claude/settings.json` for a `statusline` entry set by ccstatusline
+
+**Report status and prompt:**
+
+> "MCP/Plugins: [X/3] configured
+>   sequential-thinking: [✓ configured / ✗ missing]
+>   context7:            [✓ configured / ✗ missing]
+>   ccstatusline:        [✓ configured / ✗ missing]
+> Install missing? [y/n]"
+
+**If yes:** Follow the same install steps as `sk:setup-claude` MCP Servers & Plugins section:
+- Sequential Thinking: merge entry into `~/.mcp.json`
+- Context7: add `context7@claude-plugins-official: true` to `~/.claude/settings.json` enabledPlugins
+- ccstatusline: run `npx ccstatusline@latest`
+
+**If no:** skip, continue to Step 2.
+
+**Idempotency:** Never overwrite existing MCP entries, plugin flags, or statusline config — additive merge only.
+
 ### Step 2: Scan & Enrich
 
 After workflow update, proceeds with codebase discovery and enrichment: