claude-code-autoconfig 1.0.98 → 1.0.100

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.
@@ -1,4 +1,7 @@
1
1
  {
2
+ "env": {
3
+ "CLAUDE_CODE_DISABLE_AUTO_MEMORY": "0"
4
+ },
2
5
  "permissions": {
3
6
  "allow": [
4
7
  "Read(./**)",
package/README.md CHANGED
@@ -1,177 +1,176 @@
1
- [![npm version](https://img.shields.io/npm/v/claude-code-autoconfig.svg)](https://www.npmjs.com/package/claude-code-autoconfig)
2
- [![npm downloads](https://img.shields.io/npm/dt/claude-code-autoconfig.svg)](https://www.npmjs.com/package/claude-code-autoconfig)
3
- [![license](https://img.shields.io/npm/l/claude-code-autoconfig.svg)](https://github.com/design-and-deliver/claude-code-autoconfig/blob/main/LICENSE)
4
-
5
- # Claude Code Autoconfig
6
-
7
- Intelligent, self-configuring setup for Claude Code. One command analyzes your project, configures Claude, and shows you what it did.
8
-
9
- ## Why
10
-
11
- Claude Code is powerful out of the box, but every new project means manually writing CLAUDE.md, configuring settings.json, setting up slash commands, and tuning permissions for your stack. It's repetitive, easy to get wrong, and most developers skip it entirely — leaving Claude underinformed about their project.
12
-
13
- **Autoconfig does it in one step.** Run `/autoconfig` and Claude scans your project, detects your tech stack, and generates a tailored configuration. No templates to fill in. No boilerplate to copy-paste.
14
-
15
- ## Quick Install
16
-
17
- **npm:**
18
- ```bash
19
- npx claude-code-autoconfig
20
- ```
21
-
22
- **macOS / Linux / WSL:**
23
- ```bash
24
- curl -fsSL https://raw.githubusercontent.com/design-and-deliver/claude-code-autoconfig/main/install.sh | bash
25
- ```
26
-
27
- **Windows (PowerShell):**
28
- ```powershell
29
- irm https://raw.githubusercontent.com/design-and-deliver/claude-code-autoconfig/main/install.ps1 | iex
30
- ```
31
-
32
- ## After Install
33
-
34
- 1. **`/autoconfig`** — Claude analyzes your project and configures itself
35
- 2. **`/show-docs`** — Opens an interactive guide showing what got set up
36
-
37
- That's it. Your Claude Code environment is configured and ready.
38
-
39
- ## What Gets Installed
40
-
41
- ```
42
- your-project/
43
- ├── CLAUDE.md # Project context (auto-populated)
44
- └── .claude/
45
- ├── commands/ # Slash commands
46
- │ ├── autoconfig.md # /autoconfig - self-configures
47
- │ ├── autoconfig-update.md # /autoconfig-update - install updates
48
- │ ├── commit-and-push.md # /commit-and-push - git workflow
49
- │ ├── enable-retro.md # /enable-retro - opt-in tech debt tracking
50
- │ ├── show-docs.md # /show-docs - interactive walkthrough
51
- │ ├── sync-claude-md.md # /sync-claude-md - update CLAUDE.md
52
- │ └── test.md # /test - run tests
53
- ├── agents/ # Agent definitions
54
- │ ├── create-retro-item.md # Retro item creation agent
55
- │ └── docs-refresh.md # Docs sync agent
56
- ├── feedback/ # Team corrections for Claude
57
- │ └── FEEDBACK.md # Add entries when Claude errs
58
- ├── hooks/ # Hook scripts
59
- │ └── format.js # Auto-format on Write/Edit
60
- ├── docs/ # Interactive documentation
61
- │ └── autoconfig.docs.html # Open with /show-docs
62
- ├── updates/ # Pending config updates
63
- ├── rules/ # Path-scoped context (empty)
64
- ├── .mcp.json # MCP server configs (empty placeholder)
65
- └── settings.json # Permissions & security
66
- ```
67
-
68
- ## How It Works
69
-
70
- ### Self-Configuration
71
-
72
- Most Claude Code templates are static — copy, paste, manually fill in the blanks. If your project changes, your config is already stale.
73
-
74
- Autoconfig is **self-configuring**. Run `/autoconfig` and Claude:
75
-
76
- 1. **Detects your environment** — Windows, macOS, or Linux
77
- 2. **Scans your project** — Package files, framework indicators, test setup
78
- 3. **Populates CLAUDE.md** — Project name, tech stack, commands, conventions
79
- 4. **Configures settings.json** — Permissions tuned to your ecosystem
80
-
81
- **Supported stacks:** JavaScript/TypeScript, Python, Rust, Go, Ruby, Java, .NET, PHP
82
-
83
- | Feature | JS/TS | Python, Rust, Go, Ruby, Java, .NET, PHP |
84
- |---------|-------|------------------------------------------|
85
- | CLAUDE.md introspection | Yes | Yes |
86
- | Slash commands | Yes | Yes |
87
- | MEMORY.md | Yes | Yes |
88
- | Update system | Yes | Yes |
89
- | Auto-format hook | Yes | Coming soon |
90
- | Optimized permissions | Yes | Coming soon |
91
-
92
- Run `/sync-claude-md` anytime your project evolves to keep the configuration current.
93
-
94
- ### Slash Commands
95
-
96
- | Command | Description |
97
- |---------|-------------|
98
- | `/autoconfig` | Analyzes project and populates configuration |
99
- | `/autoconfig-update` | Check for and install configuration updates |
100
- | `/sync-claude-md` | Re-analyzes project and updates CLAUDE.md |
101
- | `/show-docs` | Opens interactive docs in browser |
102
- | `/test` | Runs your test suite (auto-detects framework) |
103
- | `/commit-and-push` | Stages, commits with good message, and pushes |
104
- | `/enable-retro` | (Experimental) Enable tech debt tracking |
105
-
106
- ### Updates
107
-
108
- When new features or improvements are released, just run the install again:
109
-
110
- ```bash
111
- npx claude-code-autoconfig@latest
112
- ```
113
-
114
- Autoconfig detects existing installations and automatically launches `/autoconfig-update` instead of a full reconfigure. Your customizations (feedback, hooks, settings) are preserved — only new files are added.
115
-
116
- Use `--force` for a clean slate reset if needed:
117
-
118
- ```bash
119
- npx claude-code-autoconfig@latest --force
120
- ```
121
-
122
- ### MEMORY.md
123
-
124
- Autoconfig writes a debug methodology to Claude's persistent memory (`MEMORY.md`), ensuring Claude investigates root causes with evidence before jumping to fixes. This loads into every future session automatically.
125
-
126
- ### Team Feedback
127
-
128
- When Claude makes a mistake, add an entry to `.claude/feedback/FEEDBACK.md`:
129
-
130
- ```markdown
131
- ## 2026-01-07: Don't use deprecated API
132
- Claude used `oldFunction()` instead of `newFunction()`.
133
- Always use the v2 API for user endpoints.
134
- ```
135
-
136
- Claude reads this directory and learns for next time. Persists across `/autoconfig` runs.
137
-
138
- ### Retro Items (Experimental)
139
-
140
- Opt-in feature for tracking tech debt. Run `/enable-retro` to activate.
141
-
142
- When enabled, Claude logs improvement opportunities as structured story files in `.claude/retro/`:
143
- - Problem description
144
- - Acceptance criteria
145
- - Suggested approach
146
- - Priority & effort sizing
147
- - Files involved
148
-
149
- Work through items anytime: *"Hey Claude, fix retro #001"*
150
-
151
- ### Rules
152
-
153
- The `rules/` directory is intentionally empty. Effective rules require understanding your codebase patterns, team conventions, and quality standards.
154
-
155
- **Want optimized rules for your project?**
156
- Reach out: [info@adac1001.com](mailto:info@adac1001.com)
157
-
158
- ## Permissions & Security
159
-
160
- The included `settings.json` provides sensible defaults that balance productivity with safety:
161
-
162
- - **`allow`** — Auto-approved operations (file edits, tests, git commands)
163
- - **`deny`** — Always blocked (secrets, destructive commands, network calls)
164
-
165
- Review and adjust these for your team's needs.
166
-
167
- See [Claude Code Security Docs](https://docs.anthropic.com/en/docs/claude-code/security) for best practices.
168
-
169
- ## Links
170
-
171
- - [npm package](https://www.npmjs.com/package/claude-code-autoconfig)
172
- - [Claude Code Docs](https://docs.anthropic.com/en/docs/claude-code/overview)
173
- - [Slash Commands Reference](https://docs.anthropic.com/en/docs/claude-code/slash-commands)
174
-
175
- ---
176
-
177
- Built by [Andrew Ciccarelli](https://www.linkedin.com/in/andrewciccarelli/) at [ADAC 1001](https://adac1001.com) — a solo dev who ships.
1
+ [![npm version](https://img.shields.io/npm/v/claude-code-autoconfig.svg)](https://www.npmjs.com/package/claude-code-autoconfig)
2
+ [![npm downloads](https://img.shields.io/npm/dt/claude-code-autoconfig.svg)](https://www.npmjs.com/package/claude-code-autoconfig)
3
+ [![license](https://img.shields.io/npm/l/claude-code-autoconfig.svg)](https://github.com/design-and-deliver/claude-code-autoconfig/blob/main/LICENSE)
4
+
5
+ # Claude Code Autoconfig
6
+
7
+ Intelligent, self-configuring setup for Claude Code. One command analyzes your project, configures Claude, and shows you what it did.
8
+
9
+ ## Why
10
+
11
+ Claude Code is powerful out of the box, but every new project means manually writing CLAUDE.md, configuring settings.json, setting up slash commands, and tuning permissions for your stack. It's repetitive, easy to get wrong, and most developers skip it entirely — leaving Claude underinformed about their project.
12
+
13
+ **Autoconfig does it in one step.** Run `/autoconfig` and Claude scans your project, detects your tech stack, and generates a tailored configuration. No templates to fill in. No boilerplate to copy-paste.
14
+
15
+ ## Quick Install
16
+
17
+ **npm:**
18
+ ```bash
19
+ npx claude-code-autoconfig
20
+ ```
21
+
22
+ **macOS / Linux / WSL:**
23
+ ```bash
24
+ curl -fsSL https://raw.githubusercontent.com/design-and-deliver/claude-code-autoconfig/main/install.sh | bash
25
+ ```
26
+
27
+ **Windows (PowerShell):**
28
+ ```powershell
29
+ irm https://raw.githubusercontent.com/design-and-deliver/claude-code-autoconfig/main/install.ps1 | iex
30
+ ```
31
+
32
+ ## After Install
33
+
34
+ 1. **`/autoconfig`** — Claude analyzes your project and configures itself
35
+ 2. **`/show-docs`** — Opens an interactive guide showing what got set up
36
+
37
+ That's it. Your Claude Code environment is configured and ready.
38
+
39
+ ## What Gets Installed
40
+
41
+ ```
42
+ your-project/
43
+ ├── CLAUDE.md # Project context (auto-populated)
44
+ └── .claude/
45
+ ├── commands/ # Slash commands
46
+ │ ├── autoconfig.md # /autoconfig - self-configures
47
+ │ ├── autoconfig-update.md # /autoconfig-update - install updates
48
+ │ ├── commit-and-push.md # /commit-and-push - git workflow
49
+ │ ├── enable-retro.md # /enable-retro - opt-in tech debt tracking
50
+ │ ├── show-docs.md # /show-docs - interactive walkthrough
51
+ │ ├── sync-claude-md.md # /sync-claude-md - update CLAUDE.md
52
+ │ └── test.md # /test - run tests
53
+ ├── agents/ # Agent definitions
54
+ │ ├── create-retro-item.md # Retro item creation agent
55
+ │ └── docs-refresh.md # Docs sync agent
56
+ ├── feedback/ # Team corrections for Claude
57
+ │ └── FEEDBACK.md # Add entries when Claude errs
58
+ ├── hooks/ # Hook scripts
59
+ │ └── format.js # Auto-format on Write/Edit
60
+ ├── docs/ # Interactive documentation
61
+ │ └── autoconfig.docs.html # Open with /show-docs
62
+ ├── updates/ # Pending config updates
63
+ ├── rules/ # Path-scoped context (empty)
64
+ ├── .mcp.json # MCP server configs (empty placeholder)
65
+ └── settings.json # Permissions & security
66
+ ```
67
+
68
+ ## How It Works
69
+
70
+ ### Self-Configuration
71
+
72
+ Most Claude Code templates are static — copy, paste, manually fill in the blanks. If your project changes, your config is already stale.
73
+
74
+ Autoconfig is **self-configuring**. Run `/autoconfig` and Claude:
75
+
76
+ 1. **Detects your environment** — Windows, macOS, or Linux
77
+ 2. **Scans your project** — Package files, framework indicators, test setup
78
+ 3. **Populates CLAUDE.md** — Project name, tech stack, commands, conventions
79
+ 4. **Configures settings.json** — Permissions tuned to your ecosystem
80
+
81
+ **Supported stacks:** JavaScript/TypeScript, Python, Rust, Go, Ruby, Java, .NET, PHP
82
+
83
+ | Feature | JS/TS | Python, Rust, Go, Ruby, Java, .NET, PHP |
84
+ |---------|-------|------------------------------------------|
85
+ | CLAUDE.md introspection | Yes | Yes |
86
+ | Slash commands | Yes | Yes |
87
+ | MEMORY.md | Yes | Yes |
88
+ | Auto-format hook | Yes | Coming soon |
89
+ | Optimized permissions | Yes | Coming soon |
90
+
91
+ Run `/sync-claude-md` anytime your project evolves to keep the configuration current.
92
+
93
+ ### Slash Commands
94
+
95
+ | Command | Description |
96
+ |---------|-------------|
97
+ | `/autoconfig` | Analyzes project and populates configuration |
98
+ | `/autoconfig-update` | Check for and install configuration updates |
99
+ | `/sync-claude-md` | Re-analyzes project and updates CLAUDE.md |
100
+ | `/show-docs` | Opens interactive docs in browser |
101
+ | `/test` | Runs your test suite (auto-detects framework) |
102
+ | `/commit-and-push` | Stages, commits with good message, and pushes |
103
+ | `/enable-retro` | (Experimental) Enable tech debt tracking |
104
+
105
+ ### Updates
106
+
107
+ When new features or improvements are released, just run the install again:
108
+
109
+ ```bash
110
+ npx claude-code-autoconfig@latest
111
+ ```
112
+
113
+ Autoconfig detects existing installations and automatically launches `/autoconfig-update` instead of a full reconfigure. Your customizations (feedback, hooks, settings) are preserved — only new files are added.
114
+
115
+ Use `--force` for a clean slate reset if needed:
116
+
117
+ ```bash
118
+ npx claude-code-autoconfig@latest --force
119
+ ```
120
+
121
+ ### MEMORY.md
122
+
123
+ Autoconfig writes a debug methodology to Claude's persistent memory (`MEMORY.md`), ensuring Claude investigates root causes with evidence before jumping to fixes. This loads into every future session automatically.
124
+
125
+ ### Team Feedback
126
+
127
+ When Claude makes a mistake, add an entry to `.claude/feedback/FEEDBACK.md`:
128
+
129
+ ```markdown
130
+ ## 2026-01-07: Don't use deprecated API
131
+ Claude used `oldFunction()` instead of `newFunction()`.
132
+ Always use the v2 API for user endpoints.
133
+ ```
134
+
135
+ Claude reads this directory and learns for next time. Persists across `/autoconfig` runs.
136
+
137
+ ### Retro Items (Experimental)
138
+
139
+ Opt-in feature for tracking tech debt. Run `/enable-retro` to activate.
140
+
141
+ When enabled, Claude logs improvement opportunities as structured story files in `.claude/retro/`:
142
+ - Problem description
143
+ - Acceptance criteria
144
+ - Suggested approach
145
+ - Priority & effort sizing
146
+ - Files involved
147
+
148
+ Work through items anytime: *"Hey Claude, fix retro #001"*
149
+
150
+ ### Rules
151
+
152
+ The `rules/` directory is intentionally empty. Effective rules require understanding your codebase patterns, team conventions, and quality standards.
153
+
154
+ **Want optimized rules for your project?**
155
+ Reach out: [info@adac1001.com](mailto:info@adac1001.com)
156
+
157
+ ## Permissions & Security
158
+
159
+ The included `settings.json` provides sensible defaults that balance productivity with safety:
160
+
161
+ - **`allow`** — Auto-approved operations (file edits, tests, git commands)
162
+ - **`deny`** — Always blocked (secrets, destructive commands, network calls)
163
+
164
+ Review and adjust these for your team's needs.
165
+
166
+ See [Claude Code Security Docs](https://docs.anthropic.com/en/docs/claude-code/security) for best practices.
167
+
168
+ ## Links
169
+
170
+ - [npm package](https://www.npmjs.com/package/claude-code-autoconfig)
171
+ - [Claude Code Docs](https://docs.anthropic.com/en/docs/claude-code/overview)
172
+ - [Slash Commands Reference](https://docs.anthropic.com/en/docs/claude-code/slash-commands)
173
+
174
+ ---
175
+
176
+ Built by [Andrew Ciccarelli](https://www.linkedin.com/in/andrewciccarelli/) at [ADAC 1001](https://adac1001.com) — a solo dev who ships.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "claude-code-autoconfig",
3
- "version": "1.0.98",
3
+ "version": "1.0.100",
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",