claude-code-autoconfig 1.0.117 → 1.0.118
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -0,0 +1,73 @@
|
|
|
1
|
+
<!-- @title Feedback to Rules Migration -->
|
|
2
|
+
<!-- @type feature -->
|
|
3
|
+
<!-- @description Scans FEEDBACK.md for entries that would be more reliably delivered as .claude/rules/ files -->
|
|
4
|
+
<!-- @files .claude/feedback/FEEDBACK.md, .claude/rules/ -->
|
|
5
|
+
|
|
6
|
+
# Migrate Rule-Eligible Feedback Entries
|
|
7
|
+
|
|
8
|
+
## Step 1: Read FEEDBACK.md
|
|
9
|
+
|
|
10
|
+
Read `.claude/feedback/FEEDBACK.md` in its entirety.
|
|
11
|
+
|
|
12
|
+
## Step 2: Evaluate entries
|
|
13
|
+
|
|
14
|
+
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.
|
|
15
|
+
|
|
16
|
+
**Rule-eligible examples:**
|
|
17
|
+
- "When editing Python files, always check imports" → `*.py`
|
|
18
|
+
- "React components should use functional style" → `*.tsx`
|
|
19
|
+
- "SQL migrations must include rollback" → `*.sql`
|
|
20
|
+
- "API route handlers need auth middleware" → `src/api/**`
|
|
21
|
+
- "CadQuery boolean unions need clearance gaps" → `*.py`
|
|
22
|
+
|
|
23
|
+
**NOT rule-eligible (keep in FEEDBACK.md):**
|
|
24
|
+
- Debugging methodology (applies to all investigation)
|
|
25
|
+
- Communication/process guidance ("confirm before coding")
|
|
26
|
+
- Meta-config guidelines (update system, versioning)
|
|
27
|
+
- Anything that applies regardless of which files are open
|
|
28
|
+
|
|
29
|
+
## Step 3: Present candidates
|
|
30
|
+
|
|
31
|
+
If no entries qualify, output:
|
|
32
|
+
|
|
33
|
+
> No rule-eligible entries found in FEEDBACK.md. Everything looks good where it is.
|
|
34
|
+
|
|
35
|
+
Then stop.
|
|
36
|
+
|
|
37
|
+
If candidates are found, present them:
|
|
38
|
+
|
|
39
|
+
```
|
|
40
|
+
FEEDBACK.md contains entries that could be more reliably delivered as .claude/rules/ files.
|
|
41
|
+
Rules auto-inject when matching files are touched — more deterministic than FEEDBACK.md.
|
|
42
|
+
|
|
43
|
+
Candidates:
|
|
44
|
+
|
|
45
|
+
1. "{entry summary}" → .claude/rules/{suggested-name}.md (glob: {pattern})
|
|
46
|
+
2. "{entry summary}" → .claude/rules/{suggested-name}.md (glob: {pattern})
|
|
47
|
+
|
|
48
|
+
Would you like me to migrate these? [y/n]
|
|
49
|
+
```
|
|
50
|
+
|
|
51
|
+
Wait for the user to confirm.
|
|
52
|
+
|
|
53
|
+
## Step 4: Migrate (if confirmed)
|
|
54
|
+
|
|
55
|
+
For each confirmed candidate:
|
|
56
|
+
|
|
57
|
+
1. Create `.claude/rules/{name}.md` with this structure:
|
|
58
|
+
```markdown
|
|
59
|
+
---
|
|
60
|
+
globs: {glob-pattern}
|
|
61
|
+
---
|
|
62
|
+
|
|
63
|
+
{migrated content from FEEDBACK.md}
|
|
64
|
+
```
|
|
65
|
+
|
|
66
|
+
2. Remove the migrated entry from FEEDBACK.md
|
|
67
|
+
|
|
68
|
+
3. Report each migration:
|
|
69
|
+
```
|
|
70
|
+
✅ Migrated "{entry}" → .claude/rules/{name}.md (glob: {pattern})
|
|
71
|
+
```
|
|
72
|
+
|
|
73
|
+
If the user declines, do nothing — the entries stay in FEEDBACK.md.
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "claude-code-autoconfig",
|
|
3
|
-
"version": "1.0.
|
|
3
|
+
"version": "1.0.118",
|
|
4
4
|
"description": "Intelligent, self-configuring setup for Claude Code. One command analyzes your project, configures Claude, and shows you what it did.",
|
|
5
5
|
"author": "ADAC 1001 <info@adac1001.com>",
|
|
6
6
|
"license": "MIT",
|