claude-code-autoconfig 1.0.5 → 1.0.7
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.
|
@@ -4,6 +4,67 @@
|
|
|
4
4
|
|
|
5
5
|
Analyze this project and configure Claude Code with real context.
|
|
6
6
|
|
|
7
|
+
## Step 0: Migrate Existing Configuration
|
|
8
|
+
|
|
9
|
+
Check for existing Claude Code configuration and migrate to the new structure.
|
|
10
|
+
|
|
11
|
+
### 0a. AGENTS.md → .claude/agents/
|
|
12
|
+
|
|
13
|
+
If an `AGENTS.md` file exists (at root or in `.claude/`):
|
|
14
|
+
1. Parse each agent definition (usually separated by headings)
|
|
15
|
+
2. Create individual files in `.claude/agents/` named after the agent (kebab-case)
|
|
16
|
+
3. Each file should contain that agent's prompt/instructions
|
|
17
|
+
4. Delete or rename the original AGENTS.md to AGENTS.md.migrated
|
|
18
|
+
5. Notify: "Migrated X agents from AGENTS.md to .claude/agents/"
|
|
19
|
+
|
|
20
|
+
### 0b. RULES.md → .claude/rules/
|
|
21
|
+
|
|
22
|
+
If a `RULES.md` file exists or CLAUDE.md contains a "Rules" section:
|
|
23
|
+
1. Extract rule definitions
|
|
24
|
+
2. Create appropriate rule files in `.claude/rules/` based on path patterns
|
|
25
|
+
3. Notify: "Migrated rules to .claude/rules/"
|
|
26
|
+
|
|
27
|
+
### 0c. Custom Commands → .claude/commands/
|
|
28
|
+
|
|
29
|
+
If CLAUDE.md contains custom slash command definitions:
|
|
30
|
+
1. Extract each command definition
|
|
31
|
+
2. Create `.claude/commands/[command-name].md` for each
|
|
32
|
+
3. Notify: "Migrated X custom commands to .claude/commands/"
|
|
33
|
+
|
|
34
|
+
### 0d. Team Feedback → .claude/feedback/
|
|
35
|
+
|
|
36
|
+
If CLAUDE.md contains **team feedback** (corrections, preferences, warnings):
|
|
37
|
+
|
|
38
|
+
**Feedback patterns:**
|
|
39
|
+
- Corrections: "Don't use X", "Always use Y instead", "Never do Z"
|
|
40
|
+
- Preferences: "We prefer...", "Team convention is...", "Boris's setup uses..."
|
|
41
|
+
- Warnings: "Be careful with...", "Watch out for...", "This is deprecated"
|
|
42
|
+
- Custom guidance: Learned behavior or team-specific knowledge
|
|
43
|
+
- Notes about past mistakes
|
|
44
|
+
|
|
45
|
+
**NOT feedback (standard config - will be regenerated):**
|
|
46
|
+
- Project name and description
|
|
47
|
+
- Tech stack listing
|
|
48
|
+
- Build/test/run commands
|
|
49
|
+
- File structure descriptions
|
|
50
|
+
|
|
51
|
+
**If feedback found:**
|
|
52
|
+
1. Extract feedback sections
|
|
53
|
+
2. Append to `.claude/feedback/FEEDBACK.md` with header:
|
|
54
|
+
```markdown
|
|
55
|
+
## [Date]: Migrated from CLAUDE.md
|
|
56
|
+
|
|
57
|
+
[extracted feedback]
|
|
58
|
+
```
|
|
59
|
+
3. Notify: "Migrated team feedback to .claude/feedback/FEEDBACK.md"
|
|
60
|
+
|
|
61
|
+
### 0e. MCP Configs
|
|
62
|
+
|
|
63
|
+
If CLAUDE.md mentions MCP servers or tool integrations:
|
|
64
|
+
1. Extract server configurations
|
|
65
|
+
2. Add to `.claude/.mcp.json` in the mcpServers object
|
|
66
|
+
3. Notify: "Migrated MCP config to .claude/.mcp.json"
|
|
67
|
+
|
|
7
68
|
## Step 1: Detect Environment
|
|
8
69
|
|
|
9
70
|
**Operating System:**
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "claude-code-autoconfig",
|
|
3
|
-
"version": "1.0.
|
|
3
|
+
"version": "1.0.7",
|
|
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",
|