claude-code-autoconfig 1.0.130 → 1.0.131

package/.claude/commands/autoconfig.md

@@ -1,13 +1,23 @@
 <!-- @description The command you just ran. Analyzes your project and populates CLAUDE.md with real context. Re-run anytime your stack changes. -->
-<!-- @version 5 -->
+<!-- @version 6 -->
 
 # Autoconfig
 
 Analyze this project and configure Claude Code with real context.
 
-**Setup Note**: During autoconfig, prefer Glob/Read/Write tools over Bash commands. This ensures smooth setup without permission prompts. Only use Bash for opening the guide at the end.
+**Setup Note**: During autoconfig, prefer Glob/Read/Write tools over Bash commands. This ensures smooth setup without permission prompts. Only use Bash for the bootstrap step and opening the guide at the end.
 
-## Step 0: Migrate FEEDBACK.md to Discoveries (one-time)
+## Step 0a: Bootstrap files from latest package
+
+Run this Bash command to ensure you have the latest commands, docs, and config files:
+
+```bash
+npx claude-code-autoconfig@latest --bootstrap
+```
+
+This copies the latest slash commands, hooks, agents, docs, and settings into `.claude/`. It exits silently on success. If it fails (e.g., no network), continue anyway — the existing files will still work.
+
+## Step 0b: Migrate FEEDBACK.md to Discoveries (one-time)
 
 Read `.claude/feedback/FEEDBACK.md`. If it contains custom content beyond the default template header (sections after the first `---`), and `CLAUDE.md` does NOT already have a `## Discoveries` section:
 

package/.claude/feedback/FEEDBACK.md

@@ -7,63 +7,3 @@ Claude reads this file but must never write to it. When Claude discovers project
 
 ---
 
-## Debugging Methodology — Evidence Before Solutions
-
-**NEVER jump to a fix based on assumptions.** When investigating a bug:
-
-1. **Gather evidence first** — add logging, check server logs, inspect actual data
-2. **Confirm the root cause** — present findings to the user with evidence
-3. **Only then propose a fix** — based on what you observed, not what you guessed
-
-If you can't determine the root cause from code reading alone, **add diagnostic logging** and ask the user to reproduce. Do NOT:
-- Guess the root cause and immediately start coding a fix
-- Assume data mismatches without checking the actual data
-- Rewrite logic because you think values "might" differ
-
-The cost of a wrong fix is high: wasted time, unnecessary code complexity, and potentially masking the real issue.
-
----
-
-## Update System Guidelines
-
-The `.claude/updates/` directory is for updates that **require Claude to execute instructions** — writing to MEMORY.md, modifying user config, running migrations, etc.
-
-**Do NOT create update files for simple command file drops.** Command files in `.claude/commands/` are automatically installed/updated by `copyDir` in the CLI. The CLI detects new and modified commands and reports them in the console output. Creating an update file for a command that's already shipped via `copyDir` is redundant.
-
-**Rule:** If the update is just a file → put it in the right directory and let the CLI copy it. If the update needs instructions → create a `NNN-*.md` update file.
-
-**Command versioning:** Every command file must have a `<!-- @version N -->` comment (typically line 2, after `@description`). Bump the version number whenever you modify a command. The CLI parses this to show version transitions on upgrade (e.g., `↑ /recover-context (v1 → v2)`).
-
----
-
-## Design Principles
-
-- Each file should have a single responsibility (one reason to change)
-- If a file exceeds 500 LOC, it likely lacks separation of concerns — look for decomposition opportunities
-- Keep cyclomatic complexity under 10 per function — extract helper functions or simplify branching if higher
-
-## Development Rules
-
-### Testing Requirements
-
-**CRITICAL: Before committing or outputting any changes to `bin/cli.js`, you MUST run tests and verify they pass:**
-
-```bash
-npm test
-```
-
-This runs tests which validate:
-1. All box-drawing lines have consistent visual width (accounting for ANSI escape codes)
-2. Box structure is valid (correct corner and border characters)
-3. CLI install files exist and are properly configured
-
-**DO NOT commit or present code changes if tests fail.** Fix the issues first.
-
-### Box Drawing Guidelines
-
-When modifying the "READY TO CONFIGURE" box in `bin/cli.js`:
-
-1. All lines must be exactly 46 visible characters wide (including the `║` borders)
-2. ANSI escape codes (`\x1b[...m`) don't count toward visible width
-3. Place color codes outside content spacing: `\x1b[33m║\x1b[0m` + 44 chars of content + `\x1b[33m║\x1b[0m`
-4. Always run `npm test` after any box modifications

package/CLAUDE.md

@@ -37,3 +37,68 @@ npm version patch && npm publish
 See `.claude/feedback/` for corrections and guidance from the team.
 
 <!-- END AUTO-GENERATED at 2026-01-14 19:54:27 UTC — Use .claude/feedback/ for corrections. -->
+
+
+## Discoveries
+<!-- Claude: append project-specific learnings, gotchas, and context below. This section persists across /autoconfig runs. -->
+
+## Debugging Methodology — Evidence Before Solutions
+
+**NEVER jump to a fix based on assumptions.** When investigating a bug:
+
+1. **Gather evidence first** — add logging, check server logs, inspect actual data
+2. **Confirm the root cause** — present findings to the user with evidence
+3. **Only then propose a fix** — based on what you observed, not what you guessed
+
+If you can't determine the root cause from code reading alone, **add diagnostic logging** and ask the user to reproduce. Do NOT:
+- Guess the root cause and immediately start coding a fix
+- Assume data mismatches without checking the actual data
+- Rewrite logic because you think values "might" differ
+
+The cost of a wrong fix is high: wasted time, unnecessary code complexity, and potentially masking the real issue.
+
+---
+
+## Update System Guidelines
+
+The `.claude/updates/` directory is for updates that **require Claude to execute instructions** — writing to MEMORY.md, modifying user config, running migrations, etc.
+
+**Do NOT create update files for simple command file drops.** Command files in `.claude/commands/` are automatically installed/updated by `copyDir` in the CLI. The CLI detects new and modified commands and reports them in the console output. Creating an update file for a command that's already shipped via `copyDir` is redundant.
+
+**Rule:** If the update is just a file → put it in the right directory and let the CLI copy it. If the update needs instructions → create a `NNN-*.md` update file.
+
+**Command versioning:** Every command file must have a `<!-- @version N -->` comment (typically line 2, after `@description`). Bump the version number whenever you modify a command. The CLI parses this to show version transitions on upgrade (e.g., `↑ /recover-context (v1 → v2)`).
+
+---
+
+## Design Principles
+
+- Each file should have a single responsibility (one reason to change)
+- If a file exceeds 500 LOC, it likely lacks separation of concerns — look for decomposition opportunities
+- Keep cyclomatic complexity under 10 per function — extract helper functions or simplify branching if higher
+
+## Development Rules
+
+### Testing Requirements
+
+**CRITICAL: Before committing or outputting any changes to `bin/cli.js`, you MUST run tests and verify they pass:**
+
+```bash
+npm test
+```
+
+This runs tests which validate:
+1. All box-drawing lines have consistent visual width (accounting for ANSI escape codes)
+2. Box structure is valid (correct corner and border characters)
+3. CLI install files exist and are properly configured
+
+**DO NOT commit or present code changes if tests fail.** Fix the issues first.
+
+### Box Drawing Guidelines
+
+When modifying the "READY TO CONFIGURE" box in `bin/cli.js`:
+
+1. All lines must be exactly 46 visible characters wide (including the `║` borders)
+2. ANSI escape codes (`\x1b[...m`) don't count toward visible width
+3. Place color codes outside content spacing: `\x1b[33m║\x1b[0m` + 44 chars of content + `\x1b[33m║\x1b[0m`
+4. Always run `npm test` after any box modifications

package/README.md

@@ -14,7 +14,7 @@ Claude Code is powerful out of the box, but every new project means manually wri
 
 ## Quick Install
 
-**Important:** Run these commands in a regular terminal, **not** from inside a Claude Code session.
+Works from a regular terminal or from inside an existing Claude Code session.
 
 **npm:**
 ```bash
@@ -49,6 +49,8 @@ your-project/
     │   ├── autoconfig-update.md       #   /autoconfig-update - install updates
     │   ├── commit-and-push.md         #   /commit-and-push - git workflow
     │   ├── enable-retro.md            #   /enable-retro - opt-in tech debt tracking
+    │   ├── gls.md                     #   /gls - view latest screenshot
+    │   ├── recover-context.md         #   /recover-context - restore context after compaction
     │   ├── show-docs.md               #   /show-docs - interactive walkthrough
     │   ├── sync-claude-md.md          #   /sync-claude-md - update CLAUDE.md
     │   └── test.md                    #   /test - run tests
@@ -102,6 +104,8 @@ Run `/sync-claude-md` anytime your project evolves to keep the configuration cur
 | `/show-docs` | Opens interactive docs in browser |
 | `/test` | Runs your test suite (auto-detects framework) |
 | `/commit-and-push` | Stages, commits with good message, and pushes |
+| `/recover-context` | Recovers conversation context after compaction |
+| `/gls` | Views latest screenshot for visual context |
 | `/enable-retro` | (Experimental) Enable tech debt tracking |
 
 ### Updates

package/bin/cli.js

@@ -154,16 +154,8 @@ if (process.argv.includes('--pull-updates')) {
 
 const forceMode = process.argv.includes('--force');
 
-// Block interactive install from inside Claude Code sessions
-if (process.env.CLAUDECODE === '1') {
-  console.log();
-  console.log('\x1b[33m%s\x1b[0m', '⚠️  This command must be run in a regular terminal, not inside Claude Code.');
-  console.log();
-  console.log('   Open a separate terminal and run:');
-  console.log('\x1b[36m%s\x1b[0m', '   npx claude-code-autoconfig@latest');
-  console.log();
-  process.exit(1);
-}
+// Detect if running inside Claude Code session
+const insideClaude = process.env.CLAUDECODE === '1';
 
 console.log('\x1b[36m%s\x1b[0m', '🚀 Claude Code Autoconfig');
 console.log();
@@ -589,6 +581,17 @@ if (isUpgrade) {
 
 const launchCommand = isUpgrade ? '/autoconfig-update' : '/autoconfig';
 
+// --bootstrap: copy files only, exit silently (used by /autoconfig inside Claude)
+const bootstrapMode = process.argv.includes('--bootstrap');
+if (bootstrapMode || insideClaude) {
+  if (!bootstrapMode) {
+    // insideClaude without --bootstrap: show guidance
+    console.log('\x1b[32m%s\x1b[0m', `✅ Files installed. Run ${launchCommand} to continue.`);
+    console.log();
+  }
+  process.exit(0);
+}
+
 // Step 4: Show "READY" message
 console.log();
 if (isUpgrade) {

package/package.json

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