claude-code-autoconfig 1.0.115 → 1.0.117

package/.claude/commands/autoconfig.md

@@ -1,5 +1,5 @@
 <!-- @description The command you just ran. Analyzes your project and populates CLAUDE.md with real context. Re-run anytime your stack changes. -->
-<!-- @version 1 -->
+<!-- @version 2 -->
 
 # Autoconfig
 
@@ -151,10 +151,11 @@ Place this section near the top (after Tech Stack, before Commands) since versio
 **Always end with:**
 ```markdown
 ## Team Feedback
-See `.claude/feedback/` for corrections and guidance from the team.
+The contents of `.claude/feedback/FEEDBACK.md` are an extension of this file.
+Read it at the start of every session before taking any action.
 ```
 
-This pointer persists across autoconfig runs and directs Claude to team-maintained content.
+This pointer persists across autoconfig runs and ensures FEEDBACK.md guidance is reliably loaded every session.
 
 ## Step 4: Create Rules Directory
 

package/.claude/commands/gls.md

@@ -1,4 +1,4 @@
-<!-- @screenshotDir  -->
+<!-- @screenshotDir /c/Users/andre/OneDrive/Pictures/Screenshots 1 -->
 <!-- @version 1 -->
 Get the latest screenshot(s) and display them.
 

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

@@ -0,0 +1,42 @@
+#!/usr/bin/env node
+
+/**
+ * @name Feedback Rule Migration Check
+ * @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
+ */
+
+// Read hook input from stdin
+let input = '';
+process.stdin.setEncoding('utf8');
+process.stdin.on('data', chunk => input += chunk);
+process.stdin.on('end', () => {
+  try {
+    const data = JSON.parse(input);
+    const filePath = data?.tool_input?.file_path || '';
+
+    // 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'));
+
+    process.exit(0);
+  } catch (err) {
+    process.exit(0);
+  }
+});

package/.claude/settings.json

@@ -2,6 +2,19 @@
   "env": {
     "CLAUDE_CODE_DISABLE_AUTO_MEMORY": "0"
   },
+  "hooks": {
+    "PostToolUse": [
+      {
+        "matcher": "Edit|Write",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "node .claude/hooks/feedback-rule-check.js"
+          }
+        ]
+      }
+    ]
+  },
   "permissions": {
     "allow": [
       "Read(./**)",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "claude-code-autoconfig",
-  "version": "1.0.115",
+  "version": "1.0.117",
   "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",