claude-code-autoconfig 1.0.169 → 1.0.171

package/.claude/docs/autoconfig.docs.html

@@ -883,11 +883,6 @@
                                 <span class="tree-file-icon">📄</span>
                                 <span class="file">enable-retro.md</span>
                             </div>
-                            <div class="tree-item indent-3 hidden" data-info="extract-rules" data-parent="commands">
-                                <span class="tree-spacer"></span>
-                                <span class="tree-file-icon">📄</span>
-                                <span class="file">extract-rules.md</span>
-                            </div>
                             <div class="tree-item indent-3 hidden" data-info="gls" data-parent="commands">
                                 <span class="tree-spacer"></span>
                                 <span class="tree-file-icon">📄</span>
@@ -1268,7 +1263,7 @@
                 title: '.claude/ Directory',
                 desc: 'Commands, rules, settings, and these docs. Keeps configuration organized as your project grows.'
             },
-                                                                                                                                                                                                                        'rules': {
+                                                                                                                                                                                                                                    'rules': {
                 title: 'rules/',
                 desc: 'Path-scoped context that loads when Claude works on matching files.'
             },
@@ -1308,11 +1303,6 @@
                 desc: '(Experimental) Enable Claude to log tech debt it encounters into .claude/retro.<div style="margin-top: 12px;"><strong>Parameters</strong><div style="margin-top: 4px; opacity: 0.6;">None</div></div><div style="margin-top: 12px;"><strong>Responses</strong><table style="width: 100%; margin-top: 6px; border-collapse: collapse; font-size: 0.9em; text-align: left;"><tr style="text-align: left; border-bottom: 1px solid var(--border);"><th style="padding: 4px 8px 4px 0;">Status</th><th style="padding: 4px 8px 4px 0;">Description</th></tr><tr style="border-bottom: 1px solid var(--border);"><td style="padding: 4px 8px 4px 0; vertical-align: top; white-space: nowrap;"><code>success</code></td><td style="padding: 4px 8px 4px 0; vertical-align: top;">Retro enabled — Claude will log tech debt to .claude/retro/ when encountered.</td></tr></table></div><div style="margin-top: 12px;"><strong>Side Effects</strong><div style="margin-top: 4px; font-size: 0.9em;">Creates .claude/retro/README.md, adds agent, updates CLAUDE.md</div></div><div style="margin-top: 12px;"><strong>Examples</strong><div style="margin-top: 6px; background: var(--bg-elevated); border-radius: 6px; padding: 8px 12px; font-family: monospace; font-size: 0.85em;"><div><code>/enable-retro</code> <span style="opacity: 0.6;">— Activate tech debt tracking</span></div></div></div>',
                 trigger: '/enable-retro'
             },
-            'extract-rules': {
-                title: 'extract-rules.md',
-                desc: 'Scan Claude artifacts and propose structured rules for .claude/rules/<div style="margin-top: 12px;"><strong>Parameters</strong><table style="width: 100%; margin-top: 6px; border-collapse: collapse; font-size: 0.9em; text-align: left;"><tr style="text-align: left; border-bottom: 1px solid var(--border);"><th style="padding: 4px 8px 4px 0;">Name</th><th style="padding: 4px 8px 4px 0;">Type</th><th style="padding: 4px 8px 4px 0;">Required</th><th style="padding: 4px 8px 4px 0;">Description</th></tr><tr style="border-bottom: 1px solid var(--border);"><td style="padding: 4px 8px 4px 0; vertical-align: top; white-space: nowrap;"><code>mode</code></td><td style="padding: 4px 8px 4px 0; vertical-align: top;"><code>string</code></td><td style="padding: 4px 8px 4px 0; vertical-align: top;">optional</td><td style="padding: 4px 8px 4px 0; vertical-align: top;">"preview" (default) shows proposals, "apply" writes and cleans sources</td></tr></table></div><div style="margin-top: 12px;"><strong>Responses</strong><table style="width: 100%; margin-top: 6px; border-collapse: collapse; font-size: 0.9em; text-align: left;"><tr style="text-align: left; border-bottom: 1px solid var(--border);"><th style="padding: 4px 8px 4px 0;">Status</th><th style="padding: 4px 8px 4px 0;">Description</th></tr><tr style="border-bottom: 1px solid var(--border);"><td style="padding: 4px 8px 4px 0; vertical-align: top; white-space: nowrap;"><code>success</code></td><td style="padding: 4px 8px 4px 0; vertical-align: top;">Rules extracted and optionally applied with source cleanup.</td></tr><tr style="border-bottom: 1px solid var(--border);"><td style="padding: 4px 8px 4px 0; vertical-align: top; white-space: nowrap;"><code>no-rules</code></td><td style="padding: 4px 8px 4px 0; vertical-align: top;">No extractable rules found in scanned sources.</td></tr></table></div><div style="margin-top: 12px;"><strong>Side Effects</strong><div style="margin-top: 4px; font-size: 0.9em;">May create .claude/rules/ files and remove extracted content from source files</div></div><div style="margin-top: 12px;"><strong>Examples</strong><div style="margin-top: 6px; background: var(--bg-elevated); border-radius: 6px; padding: 8px 12px; font-family: monospace; font-size: 0.85em;"><div><code>/extract-rules</code> <span style="opacity: 0.6;">— Preview proposed rules without writing</span></div><div><code>/extract-rules --apply</code> <span style="opacity: 0.6;">— Write rules and clean up sources</span></div></div></div>',
-                trigger: '/extract-rules'
-            },
             'gls': {
                 title: 'gls.md',
                 desc: 'Get the latest screenshot(s) and display them.<div style="margin-top: 12px;"><strong>Parameters</strong><table style="width: 100%; margin-top: 6px; border-collapse: collapse; font-size: 0.9em; text-align: left;"><tr style="text-align: left; border-bottom: 1px solid var(--border);"><th style="padding: 4px 8px 4px 0;">Name</th><th style="padding: 4px 8px 4px 0;">Type</th><th style="padding: 4px 8px 4px 0;">Required</th><th style="padding: 4px 8px 4px 0;">Description</th></tr><tr style="border-bottom: 1px solid var(--border);"><td style="padding: 4px 8px 4px 0; vertical-align: top; white-space: nowrap;"><code>count</code></td><td style="padding: 4px 8px 4px 0; vertical-align: top;"><code>integer</code></td><td style="padding: 4px 8px 4px 0; vertical-align: top;">optional</td><td style="padding: 4px 8px 4px 0; vertical-align: top;">Number of screenshots to display. Use /gls-N syntax. Default: 1. Min: 1.</td></tr><tr style="border-bottom: 1px solid var(--border);"><td style="padding: 4px 8px 4px 0; vertical-align: top; white-space: nowrap;"><code>path</code></td><td style="padding: 4px 8px 4px 0; vertical-align: top;"><code>string</code></td><td style="padding: 4px 8px 4px 0; vertical-align: top;">optional</td><td style="padding: 4px 8px 4px 0; vertical-align: top;">Screenshot directory path. Saved for future use. Auto-detected if omitted.</td></tr></table></div><div style="margin-top: 12px;"><strong>Responses</strong><table style="width: 100%; margin-top: 6px; border-collapse: collapse; font-size: 0.9em; text-align: left;"><tr style="text-align: left; border-bottom: 1px solid var(--border);"><th style="padding: 4px 8px 4px 0;">Status</th><th style="padding: 4px 8px 4px 0;">Description</th></tr><tr style="border-bottom: 1px solid var(--border);"><td style="padding: 4px 8px 4px 0; vertical-align: top; white-space: nowrap;"><code>success</code></td><td style="padding: 4px 8px 4px 0; vertical-align: top;">Displays requested screenshot(s) from newest to oldest.</td></tr><tr style="border-bottom: 1px solid var(--border);"><td style="padding: 4px 8px 4px 0; vertical-align: top; white-space: nowrap;"><code>no-screenshots</code></td><td style="padding: 4px 8px 4px 0; vertical-align: top;">Directory exists but contains no image files.</td></tr><tr style="border-bottom: 1px solid var(--border);"><td style="padding: 4px 8px 4px 0; vertical-align: top; white-space: nowrap;"><code>no-directory</code></td><td style="padding: 4px 8px 4px 0; vertical-align: top;">Unable to detect screenshot directory — prompts for path.</td></tr></table></div><div style="margin-top: 12px;"><strong>Side Effects</strong><div style="margin-top: 4px; font-size: 0.9em;">Saves detected screenshot path to .claude/cca.config.json on first run</div></div><div style="margin-top: 12px;"><strong>Examples</strong><div style="margin-top: 6px; background: var(--bg-elevated); border-radius: 6px; padding: 8px 12px; font-family: monospace; font-size: 0.85em;"><div><code>/gls</code> <span style="opacity: 0.6;">— Display the most recent screenshot</span></div><div><code>/gls-3</code> <span style="opacity: 0.6;">— Display the 3 most recent screenshots</span></div><div><code>/gls /path/to/dir</code> <span style="opacity: 0.6;">— Use a specific screenshot directory</span></div></div></div>',
@@ -1579,7 +1569,7 @@ CRITICAL: A plausible-looking cause from code reading is NOT confirmed evidence.
 
 > Run \`/autoconfig\` to populate this based on your project.`
             },
-                                                                                                                                                                                                                        'autoconfig-update': {
+                                                                                                                                                                                                                                    'autoconfig-update': {
                 filename: 'autoconfig-update.md',
                 content: `<!-- @applied
 -->
@@ -1699,38 +1689,6 @@ Each item is a structured story file with:
 
 - "Fix retro #001" — Work on a specific item
 - "What's in the retro backlog?" — List pending items`
-            },
-            'extract-rules': {
-                filename: 'extract-rules.md',
-                content: `# Extract Rules
-
-Scan all Claude configuration artifacts and propose structured rules for \`.claude/rules/\`.
-
-## Step 0: Git safety check
-
-Before doing anything else, check for uncommitted changes:
-
-\`\`\`bash
-git status --porcelain
-\`\`\`
-
-If there are uncommitted changes, show this warning and wait for confirmation:
-
-> **Warning:** This command will modify files (extract rules from sources and optionally clean up originals). You have uncommitted changes.
->
-> Commit your work before proceeding, or type "continue" to proceed anyway.
-
-If the working tree is clean, proceed silently.
-
-## Step 1: Discover sources
-
-Scan these locations for \`.md\` files containing potential rules. **Skip any that don't exist** — not all projects have all of these:
-
-1. \`CLAUDE.md\` (project root)
-2. \`CLAUDE.local.md\` (project root, if present)
-3. All \`.md\` files in \`.claude/\` recursively (feedback, commands, etc.) — **excluding** \`.claude/rules/\` and \`.claude/commands/extract-rules.md\`
-4. Any nested \`CLAUDE.md\` files in subdirectories (e.g., \`src/CLAUDE.md\`)
-5. \`.claude/settings.json\` (hooks section — behavioral rules implied by hooks)`
             },
             'gls': {
                 filename: 'gls.md',

package/.claude/rules/deploy-approval.md

@@ -0,0 +1,8 @@
+---
+paths:
+  - "bin/cli.js"
+  - ".claude/commands/*.md"
+  - "package.json"
+---
+
+Do not publish new commands or features to npm without explicit user approval. Adding a file to the project repo is not the same as approving it for deploy. Wait for explicit "deploy", "publish", or "push it out" before running npm version + publish.

package/CHANGELOG.md

@@ -1,5 +1,11 @@
 # Changelog
 
+## v1.0.171
+- feat: /extract-rules v3 — automatic flow, --keep-sources, changelog summary
+
+## v1.0.170
+- revert: remove /extract-rules from deployed build
+
 ## v1.0.169
 - feat: add /extract-rules command
 
@@ -141,9 +147,3 @@
 ## v1.0.122
 - feat: /autoconfig pulls latest package before configuring
 
-## v1.0.121
-- feat: add feedback-to-discoveries migration update (004)
-
-## v1.0.120
-- feat: separate Claude discoveries from human feedback
-

package/README.md

@@ -49,7 +49,6 @@ 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
-    │   ├── extract-rules.md          #   /extract-rules - extract rules from artifacts
     │   ├── gls.md                     #   /gls - view latest screenshot
     │   ├── recover-context.md         #   /recover-context - restore context after compaction
     │   ├── show-docs.md               #   /show-docs - interactive walkthrough
@@ -102,7 +101,6 @@ Autoconfig is **self-configuring**. Run `/autoconfig` and Claude:
 | `/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 |
-| `/extract-rules` | Scan artifacts and propose structured rules for `.claude/rules/` |
 | `/recover-context` | Recovers conversation context after compaction |
 | `/gls` | Views latest screenshot for visual context |
 | `/validate-cca-install` | Validates installation against latest published version |

package/bin/cli.js

@@ -327,7 +327,7 @@ const hooksSrc = path.join(packageDir, '.claude', 'hooks');
 const scriptsSrc = path.join(packageDir, '.claude', 'scripts');
 
 // Files that exist in the dev repo but should never be installed to user projects
-const DEV_ONLY_FILES = ['publish.md'];
+const DEV_ONLY_FILES = ['publish.md', 'extract-rules.md'];
 
 function copyDir(src, dest) {
   fs.mkdirSync(dest, { recursive: true });

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "claude-code-autoconfig",
-  "version": "1.0.169",
+  "version": "1.0.171",
   "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",
@@ -38,6 +38,7 @@
     "!.claude/cca.config.json",
     "!.claude/.autoconfig-version",
     "!.claude/commands/publish.md",
+    "!.claude/commands/extract-rules.md",
     "!.claude/plans",
     "CLAUDE.md",
     "CHANGELOG.md"

package/.claude/commands/extract-rules.md

@@ -1,128 +0,0 @@
-<!-- @description Scan Claude artifacts and propose structured rules for .claude/rules/ -->
-<!-- @version 1 -->
-<!-- @param mode | string | optional | "preview" (default) shows proposals, "apply" writes and cleans sources -->
-<!-- @response success | Rules extracted and optionally applied with source cleanup. -->
-<!-- @response no-rules | No extractable rules found in scanned sources. -->
-<!-- @sideeffect May create .claude/rules/ files and remove extracted content from source files -->
-<!-- @example /extract-rules | Preview proposed rules without writing -->
-<!-- @example /extract-rules --apply | Write rules and clean up sources -->
-
-# Extract Rules
-
-Scan all Claude configuration artifacts and propose structured rules for `.claude/rules/`.
-
-## Step 0: Git safety check
-
-Before doing anything else, check for uncommitted changes:
-
-```bash
-git status --porcelain
-```
-
-If there are uncommitted changes, show this warning and wait for confirmation:
-
-> **Warning:** This command will modify files (extract rules from sources and optionally clean up originals). You have uncommitted changes.
->
-> Commit your work before proceeding, or type "continue" to proceed anyway.
-
-If the working tree is clean, proceed silently.
-
-## Step 1: Discover sources
-
-Scan these locations for `.md` files containing potential rules. **Skip any that don't exist** — not all projects have all of these:
-
-1. `CLAUDE.md` (project root)
-2. `CLAUDE.local.md` (project root, if present)
-3. All `.md` files in `.claude/` recursively (feedback, commands, etc.) — **excluding** `.claude/rules/` and `.claude/commands/extract-rules.md`
-4. Any nested `CLAUDE.md` files in subdirectories (e.g., `src/CLAUDE.md`)
-5. `.claude/settings.json` (hooks section — behavioral rules implied by hooks)
-
-Also read all existing `.claude/rules/` files to avoid proposing duplicates.
-
-## Step 2: Extract candidate rules
-
-A rule is a **deterministic behavioral instruction** that Claude should follow when working on specific files or file patterns. Good rules are:
-
-- **Actionable**: "Do X" or "Never do Y" — not background context
-- **Scoped**: Applies to specific files, directories, or file patterns
-- **Not already enforced**: Skip anything already handled by hooks, settings, or linting
-- **Not ephemeral**: Skip project status, session notes, debugging histories
-
-**Skip these** (they belong in other artifacts):
-- Domain knowledge / business logic explanations → stay in their source doc
-- Slash command definitions → stay in `commands/`
-- Session-specific debugging notes → stay in memory
-- Deployment / operational procedures → stay in their source doc
-
-## Step 3: Deduplicate
-
-- If a candidate rule already exists in `.claude/rules/` (same intent, even if worded differently), skip it
-- If the same guidance appears in multiple sources, note all sources but propose one rule
-- Group related rules into single files when they share the same `paths` scope. If two imperatives apply to the same files, they belong in one rule file. If they target different files, keep them separate — even if topically related.
-
-## Step 4: Rate confidence
-
-For each proposed rule, assign a confidence level:
-
-- **HIGH** — Explicit imperative instruction ("never do X", "always do Y", "must use Z", "prefer X over Y"). The source text literally contains an imperative. Extract these.
-- **SKIP** — Everything else: inferred conventions, contextual guidance, implementation details derivable from the code. Do not propose these.
-
-## Step 5: Output proposals
-
-For each HIGH-confidence rule, output:
-
-```
-### Rule: <short name>
-**Source**: <file(s) it was extracted from>
-**Paths**: <e.g., `src/background.ts`, `src/**/*.ts`, `*.ts`>
-**File name**: <proposed .claude/rules/ filename, e.g., `linkedin-selectors.md`>
-
---- file content ---
----
-paths:
-  - "src/background.ts"
-  - "src/**/*.ts"
----
-
-<rule content here>
---- end file content ---
-```
-
-The file content block must include proper YAML frontmatter with `paths` as an array. This is the exact format Claude Code expects.
-
-**Validate paths**: Before proposing a rule, use Glob to verify that at least one `paths` pattern matches existing files in the project. If no files match, flag it with `⚠️ no matching files` and exclude it from the proposal. Dead rules erode trust.
-
-At the end, show a summary table:
-
-| # | Rule file | Paths | Source(s) | Status |
-|---|-----------|-------|-----------|--------|
-
-Status column: `NEW` if no prior rule exists, `UPDATE` if it would merge with/extend an existing rule, `SKIP` if already covered.
-
-After the table, show a stats line:
-
-> Scanned **N** sources · Extracted **X** rules · Skipped **Y** candidates
-
-## Step 6: Apply or wait
-
-- **Default (preview mode)**: Do NOT create any files. Wait for user approval.
-- **If `--apply` argument is passed**: Write all proposed rules directly, then proceed to Step 7.
-
-After user approves in preview mode, write the rule files and proceed to Step 7.
-
-## Step 7: Source cleanup
-
-After writing rules, remove the extracted content from the original source files:
-
-1. For each written rule, locate the original text in the source file(s)
-2. Remove the extracted lines from the source — do not leave comments or placeholders
-3. If removing content leaves an empty section (e.g., a `## Discoveries` section with no remaining entries), remove the section heading too
-4. Preserve all non-extracted content in the source file
-
-Show what was cleaned:
-
-```
-Cleaned sources:
-  CLAUDE.md — removed 3 lines (2 rules extracted)
-  .claude/feedback/FEEDBACK.md — removed 1 line (1 rule extracted)
-```