claude-code-autoconfig 1.0.116 → 1.0.118

package/.claude/hooks/feedback-rule-check.js

@@ -2,33 +2,12 @@
 
 /**
  * @name Feedback Rule Migration Check
- * @description After FEEDBACK.md is edited, scans for entries that could be
- *              more reliably delivered as .claude/rules/ files with glob patterns.
+ * @description After FEEDBACK.md is edited, notifies Claude to evaluate
+ *              whether any entries would be more reliably delivered as
+ *              .claude/rules/ files with glob patterns.
  * @trigger PostToolUse on Write|Edit
  */
 
-const fs = require('fs');
-const path = require('path');
-
-// File extension patterns that suggest rule-eligible content
-const FILE_PATTERNS = [
-  { regex: /\*\.py\b/i, ext: '*.py', lang: 'Python' },
-  { regex: /\*\.js\b/i, ext: '*.js', lang: 'JavaScript' },
-  { regex: /\*\.jsx\b/i, ext: '*.jsx', lang: 'JSX' },
-  { regex: /\*\.ts\b/i, ext: '*.ts', lang: 'TypeScript' },
-  { regex: /\*\.tsx\b/i, ext: '*.tsx', lang: 'TSX' },
-  { regex: /\*\.go\b/i, ext: '*.go', lang: 'Go' },
-  { regex: /\*\.rs\b/i, ext: '*.rs', lang: 'Rust' },
-  { regex: /\*\.rb\b/i, ext: '*.rb', lang: 'Ruby' },
-  { regex: /\*\.java\b/i, ext: '*.java', lang: 'Java' },
-  { regex: /\*\.cpp\b|\.c\b|\.h\b/i, ext: '*.cpp', lang: 'C/C++' },
-  { regex: /\*\.css\b|\.scss\b/i, ext: '*.css', lang: 'CSS' },
-  { regex: /\*\.sql\b/i, ext: '*.sql', lang: 'SQL' },
-  { regex: /\.vue\b/i, ext: '*.vue', lang: 'Vue' },
-  { regex: /\.swift\b/i, ext: '*.swift', lang: 'Swift' },
-  { regex: /\.kt\b|\.kotlin\b/i, ext: '*.kt', lang: 'Kotlin' },
-];
-
 // Read hook input from stdin
 let input = '';
 process.stdin.setEncoding('utf8');
@@ -36,76 +15,28 @@ process.stdin.on('data', chunk => input += chunk);
 process.stdin.on('end', () => {
   try {
     const data = JSON.parse(input);
-    handleHook(data);
-  } catch (err) {
-    process.exit(0);
-  }
-});
+    const filePath = data?.tool_input?.file_path || '';
 
-function handleHook(data) {
-  const filePath = data?.tool_input?.file_path || '';
+    // Only fire for FEEDBACK.md edits
+    if (!filePath.endsWith('FEEDBACK.md')) {
+      process.exit(0);
+    }
 
-  // Only fire for FEEDBACK.md edits
-  if (!filePath.endsWith('FEEDBACK.md')) {
-    process.exit(0);
-  }
+    console.log([
+      'FEEDBACK.md was just modified.',
+      'Review the changes and evaluate whether any entries are tied to specific file types,',
+      'frameworks, or patterns that could be scoped with a glob (e.g., *.py, *.tsx, src/api/**).',
+      '',
+      'If any entries qualify, ask the user:',
+      '"Some of this guidance targets specific file types. Want me to migrate it to .claude/rules/',
+      'for more reliable delivery? Rules auto-inject when matching files are touched."',
+      '',
+      'If the user confirms, create the rule file with the appropriate glob and remove the entry from FEEDBACK.md.',
+      'If nothing qualifies, do nothing — not every FEEDBACK.md entry needs to be a rule.',
+    ].join('\n'));
 
-  // Read the updated FEEDBACK.md
-  let content;
-  try {
-    content = fs.readFileSync(filePath, 'utf8');
-  } catch (err) {
     process.exit(0);
-  }
-
-  // Scan for file-type patterns
-  const candidates = [];
-  const lines = content.split('\n');
-
-  for (let i = 0; i < lines.length; i++) {
-    const line = lines[i];
-    for (const pattern of FILE_PATTERNS) {
-      if (pattern.regex.test(line)) {
-        // Get surrounding context (the section this line belongs to)
-        let sectionStart = i;
-        while (sectionStart > 0 && !lines[sectionStart - 1].startsWith('##')) {
-          sectionStart--;
-        }
-        const sectionHeader = lines[sectionStart].startsWith('##')
-          ? lines[sectionStart].replace(/^#+\s*/, '')
-          : 'Unknown section';
-
-        candidates.push({
-          lang: pattern.lang,
-          ext: pattern.ext,
-          line: i + 1,
-          section: sectionHeader,
-          text: line.trim()
-        });
-        break; // One match per line is enough
-      }
-    }
-  }
-
-  if (candidates.length === 0) {
+  } catch (err) {
     process.exit(0);
   }
-
-  // Deduplicate by language
-  const uniqueLangs = [...new Set(candidates.map(c => c.lang))];
-
-  // Output suggestion for Claude to relay to user
-  const suggestions = uniqueLangs.map(lang => {
-    const matches = candidates.filter(c => c.lang === lang);
-    const ext = matches[0].ext;
-    return `  - ${lang} (${ext}): ${matches.length} mention${matches.length > 1 ? 's' : ''} found`;
-  }).join('\n');
-
-  console.log(`FEEDBACK.md contains guidance that references specific file types.`);
-  console.log(`These entries may be more reliably delivered as .claude/rules/ files:\n`);
-  console.log(suggestions);
-  console.log(`\nConsider asking the user if they'd like to migrate these to rules.`);
-  console.log(`Rules auto-inject when matching files are touched — more deterministic than FEEDBACK.md.`);
-
-  process.exit(0);
-}
+});

package/.claude/updates/003-feedback-to-rules-migration.md

@@ -0,0 +1,73 @@
+<!-- @title Feedback to Rules Migration -->
+<!-- @type feature -->
+<!-- @description Scans FEEDBACK.md for entries that would be more reliably delivered as .claude/rules/ files -->
+<!-- @files .claude/feedback/FEEDBACK.md, .claude/rules/ -->
+
+# Migrate Rule-Eligible Feedback Entries
+
+## Step 1: Read FEEDBACK.md
+
+Read `.claude/feedback/FEEDBACK.md` in its entirety.
+
+## Step 2: Evaluate entries
+
+Review each entry/section in FEEDBACK.md and determine whether it is tied to specific file types, frameworks, directories, or patterns that could be scoped with a glob.
+
+**Rule-eligible examples:**
+- "When editing Python files, always check imports" → `*.py`
+- "React components should use functional style" → `*.tsx`
+- "SQL migrations must include rollback" → `*.sql`
+- "API route handlers need auth middleware" → `src/api/**`
+- "CadQuery boolean unions need clearance gaps" → `*.py`
+
+**NOT rule-eligible (keep in FEEDBACK.md):**
+- Debugging methodology (applies to all investigation)
+- Communication/process guidance ("confirm before coding")
+- Meta-config guidelines (update system, versioning)
+- Anything that applies regardless of which files are open
+
+## Step 3: Present candidates
+
+If no entries qualify, output:
+
+> No rule-eligible entries found in FEEDBACK.md. Everything looks good where it is.
+
+Then stop.
+
+If candidates are found, present them:
+
+```
+FEEDBACK.md contains entries that could be more reliably delivered as .claude/rules/ files.
+Rules auto-inject when matching files are touched — more deterministic than FEEDBACK.md.
+
+Candidates:
+
+  1. "{entry summary}" → .claude/rules/{suggested-name}.md (glob: {pattern})
+  2. "{entry summary}" → .claude/rules/{suggested-name}.md (glob: {pattern})
+
+Would you like me to migrate these? [y/n]
+```
+
+Wait for the user to confirm.
+
+## Step 4: Migrate (if confirmed)
+
+For each confirmed candidate:
+
+1. Create `.claude/rules/{name}.md` with this structure:
+   ```markdown
+   ---
+   globs: {glob-pattern}
+   ---
+
+   {migrated content from FEEDBACK.md}
+   ```
+
+2. Remove the migrated entry from FEEDBACK.md
+
+3. Report each migration:
+   ```
+   ✅ Migrated "{entry}" → .claude/rules/{name}.md (glob: {pattern})
+   ```
+
+If the user declines, do nothing — the entries stay in FEEDBACK.md.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "claude-code-autoconfig",
-  "version": "1.0.116",
+  "version": "1.0.118",
   "description": "Intelligent, self-configuring setup for Claude Code. One command analyzes your project, configures Claude, and shows you what it did.",
   "author": "ADAC 1001 <info@adac1001.com>",
   "license": "MIT",