codebyplan 1.13.3 → 1.13.5

package/templates/skills/cbp-setup-eslint/reference/vitest.md

@@ -1,62 +1,42 @@
-# vitest — Vitest test-file rules
+# vitest — Vitest test files (official @vitest/eslint-plugin setup)
 
-For apps that test with Vitest (CBP web + CLI + most repos). Layers a **test-scoped** override
-on top of [base](base.md). Maps to the CBP **`testing`** DB preset
-(`tech_match.requires: ["Vitest"]`).
+> **Official source**: https://github.com/vitest-dev/eslint-plugin-vitest (verified 2026-05-31). This
+> is the plugin's official flat-config example verbatim.
 
-> **Verified 2026-05-31.** The package was **renamed** to the scoped
-> **`@vitest/eslint-plugin`** (the old `eslint-plugin-vitest` is the deprecated name). Its
-> flat-config key is plain **`configs.recommended`** — there is **no `flat/` prefix**.
+> The package was renamed from `eslint-plugin-vitest` to the scoped **`@vitest/eslint-plugin`**.
 
-## Packages
-
-| Package | Latest | Purpose |
-| ------- | ------ | ------- |
-| `@vitest/eslint-plugin` | `1.6.18` | Vitest rules (scoped pkg) |
+## Install
 
 ```bash
-pnpm add -D @vitest/eslint-plugin
+npm install @vitest/eslint-plugin --save-dev
 ```
 
-## Flat config
+## eslint.config.mjs (official example)
 
 ```js
-// eslint.config.mjs
+import { defineConfig } from "eslint/config";
 import vitest from "@vitest/eslint-plugin";
 
-export default [
-  {
-    files: ["**/*.{test,spec}.{ts,tsx,js,jsx}"],
-    plugins: { vitest },
-    rules: {
-      ...vitest.configs.recommended.rules,
-      // tests are I/O-heavy + mock-heavy — relax type-safety on test files:
-      "@typescript-eslint/no-explicit-any": "off",
-      "@typescript-eslint/no-unsafe-assignment": "off",
-      "@typescript-eslint/no-unsafe-member-access": "off",
-      "@typescript-eslint/no-unsafe-call": "off",
-      "@typescript-eslint/no-unsafe-argument": "off",
-      "@typescript-eslint/no-unsafe-return": "off",
-    },
-    settings: { vitest: { typecheck: true } }, // only if using Vitest type-testing
+export default defineConfig({
+  files: ["tests/**"], // or any other pattern
+  plugins: {
+    vitest,
+  },
+  rules: {
+    ...vitest.configs.recommended.rules,
+    "vitest/max-nested-describe": ["error", { max: 3 }],
   },
-];
+});
 ```
 
-## Gotchas
-
-- The key is **`vitest.configs.recommended`** (plain) — NOT `configs['flat/recommended']`.
-  Other plugins use the bracketed `flat/` form; Vitest does not.
-- When you spread only `.rules`, register `plugins: { vitest }` yourself. Alternatively spread
-  the whole `...vitest.configs.recommended` (carries the plugin registration).
-- The `no-unsafe-*` / `no-explicit-any` opt-outs are CBP convention — production code keeps
-  them at `error`; test surfaces relax them because mocks produce `any`-typed values.
-
-## CBP preset divergence
+## Notes (from the official docs)
 
-The CBP `testing` preset matches this (the six `no-unsafe-*`/`no-explicit-any` opt-outs,
-`@vitest/eslint-plugin: ^1.0.0`). No divergence.
+- The config key is **`vitest.configs.recommended`** — there is **no `flat/` prefix** (unlike most
+  other test plugins). Variants: `configs.recommended` and `configs.all`.
+- Register `plugins: { vitest }` yourself when spreading only `.rules`.
+- Scope to your test files via `files`. Vitest type-testing uses a separate `typecheck: true` setting.
+- The README still shows legacy `.eslintrc` JSON for ESLint ≤ v8.57.0 alongside flat config.
 
-## Official docs
+## Source
 
-- @vitest/eslint-plugin: https://github.com/vitest-dev/eslint-plugin-vitest
+- https://github.com/vitest-dev/eslint-plugin-vitest

package/templates/hooks/cbp-notify.sh

@@ -1,68 +0,0 @@
-#!/bin/bash
-# @hook: Notification
-# Hook: Notification for all matchers
-# Purpose: Send desktop notifications with project context. Cross-platform graceful-degrade —
-#          silent no-op when terminal-notifier is missing (Linux/Windows/macOS without Homebrew);
-#          VS Code click-to-focus action only on macOS hosts with `code` on PATH.
-# Exit 0 = always (notification hooks must never block Claude)
-#
-# Known: notification_type is not sent in JSON input (anthropics/claude-code#11964)
-# Input fields: session_id, cwd, hook_event_name, message
-
-set +e
-
-# Graceful skip on hosts without terminal-notifier (Linux, Windows, macOS w/o Homebrew)
-command -v terminal-notifier >/dev/null 2>&1 || exit 0
-
-# Read JSON input from stdin
-INPUT=$(cat)
-
-# Parse notification fields
-eval "$(echo "$INPUT" | jq -r '
-  @sh "MESSAGE=\(.message // "")",
-  @sh "CWD=\(.cwd // "")"
-' 2>/dev/null)"
-
-# Detect project name
-if [ -n "$CLAUDE_PROJECT_DIR" ]; then
-  PROJECT_DIR="$CLAUDE_PROJECT_DIR"
-elif [ -n "$CWD" ]; then
-  PROJECT_DIR="$CWD"
-else
-  PROJECT_DIR="unknown"
-fi
-PROJECT_NAME=$(basename "$PROJECT_DIR")
-
-TITLE="[$PROJECT_NAME] Claude Code"
-BODY="${MESSAGE:-Claude Code notification}"
-
-# VS Code focus click action — only on macOS with `code` available
-CLICK_ACTION=""
-if [[ "$OSTYPE" == darwin* ]] && command -v code >/dev/null 2>&1; then
-  # Quote path for re-parse by terminal-notifier -execute (POSIX sh)
-  SAFE_DIR=$(printf '%q' "$PROJECT_DIR")
-  CLICK_ACTION="code -r $SAFE_DIR && sleep 0.3 && osascript -e 'tell application \"System Events\" to keystroke \"\`\" using control down'"
-fi
-
-# Send notification via terminal-notifier in background (non-blocking).
-# Omit -execute argument entirely when CLICK_ACTION is empty (avoid passing empty string).
-if [ -n "$CLICK_ACTION" ]; then
-  terminal-notifier \
-    -title "$TITLE" \
-    -message "$BODY" \
-    -sound "Glass" \
-    -group "claude-${PROJECT_NAME}" \
-    -execute "$CLICK_ACTION" \
-    -sender "com.microsoft.VSCode" \
-    > /dev/null 2>&1 &
-else
-  terminal-notifier \
-    -title "$TITLE" \
-    -message "$BODY" \
-    -sound "Glass" \
-    -group "claude-${PROJECT_NAME}" \
-    -sender "com.microsoft.VSCode" \
-    > /dev/null 2>&1 &
-fi
-
-exit 0