claude-code-autoconfig: Instructions file for Claude Code

claude-code-autoconfig

CLI tool that auto-configures Claude Code for any project. One command analyzes your project, configures Claude, and shows you what it did.

Tech Stack

• Runtime: Node.js (>=18.0.0)
• Type: npm CLI package
• Entry: bin/cli.js

Commands

npm test          # Run ALL tests (full suite — see Testing Requirements below)
npm run test:box  # Run box alignment tests only
npm run test:install # Run CLI install tests only

Project Structure

• bin/cli.js — Main CLI entry point, handles bootstrap and /autoconfig launch
• .claude/commands/ — Slash command definitions (/autoconfig, /autoconfig-update, etc.)
• .claude/hooks/ — Hook scripts (format.js for JS/TS projects)
• .claude/feedback/ — Team feedback and corrections
• test/ — Test files

Publishing

npm version patch && npm publish

After publish, push the branch AND the release tag explicitly (the postversion changelog hook re-tags lightweight): git push origin main && git push origin v<x.y.z>.

Changelog is user-facing — write commits accordingly

CHANGELOG.md regenerates from commit subjects on every npm version, and the installer shows those bullets verbatim to users on upgrade (bin/update-summary.js). So:

• Subjects may stay technical, but then the commit body MUST carry a plain-language trailer the changelog uses instead: Changelog: More reliable 'awaiting your reply' tab indicator. Write it for a CCA user, not a maintainer — name the visible outcome, never internals (no hook/regex/TDZ/function names).
• Changelog: none (or skip) hides an internal-only commit from the changelog.
• Keep the feat:/fix: conventional prefix on the subject — it drives the summary's "New features" vs "Fixes & improvements" grouping.
• Already-pushed commits can't be reworded in git; add a row to OVERRIDES in scripts/generate-changelog.js instead (value null drops the bullet). New work never uses OVERRIDES — author the trailer.