claude-config-doctor 0.2.2

package/.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,45 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at https://www.contributorcovenant.org/version/1/4/code-of-conduct.html.
+
+[homepage]: https://www.contributorcovenant.org

package/.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,39 @@
+name: Bug Report
+description: Report a bug to help us improve.
+labels: [bug]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to report a bug! Please fill out the information below.
+  - type: textarea
+    id: description
+    attributes:
+      label: Description
+      description: A clear and concise description of what the bug is.
+    validations:
+      required: true
+  - type: textarea
+    id: reproduction
+    attributes:
+      label: Reproduction Steps
+      description: Steps to recreate the issue.
+      placeholder: |
+        1. Run `npx claude-config-doctor check`
+        2. Observer error...
+    validations:
+      required: true
+  - type: textarea
+    id: expected
+    attributes:
+      label: Expected Behavior
+      description: What should happen instead.
+    validations:
+      required: true
+  - type: textarea
+    id: context
+    attributes:
+      label: Environment Info
+      description: OS version, Bun/Node version, etc.
+    validations:
+      required: true

package/.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,23 @@
+name: Feature Request
+description: Suggest an enhancement.
+labels: [enhancement]
+body:
+  - type: textarea
+    id: feature
+    attributes:
+      label: Summary
+      description: A clear and concise description of the feature request.
+    validations:
+      required: true
+  - type: textarea
+    id: use-case
+    attributes:
+      label: Use Case
+      description: What problem would this solve for you?
+    validations:
+      required: true
+  - type: textarea
+    id: alternative
+    attributes:
+      label: Alternatives Considered
+      description: Any other ways you've tried to achieve this.

package/.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,19 @@
+# PR Template
+
+## 🚀 Impact
+
+Describe the problem this solves and how it improves the experience for Claude Code users.
+
+Fixes # (issue)
+
+## 🩺 Verification & Tests
+
+How did you verify this change?
+
+- [ ] `bun run test` passes.
+- [ ] `bun run lint` passes.
+- [ ] I've manually verified with a sample config (share command/output if relevant).
+
+## 📸 CLI Output (Optional)
+
+If this changes the CLI output, share a quick snippet or screenshot of the new report format!

package/.github/workflows/ci.yml

@@ -0,0 +1,27 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+    branches: [main]
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: actions/checkout@v3
+      - name: Setup Bun
+        uses: oven-sh/setup-bun@v2
+        with:
+          bun-version: latest
+
+      - name: Install dependencies
+        run: bun install
+
+      - name: Lint and Format
+        run: bun run lint
+
+      - name: Run tests
+        run: bun test

package/.github/workflows/release.yml

@@ -0,0 +1,66 @@
+name: Release & Publish
+
+on:
+  push:
+    branches:
+      - main
+
+jobs:
+  release:
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write
+    steps:
+      - uses: actions/checkout@v3
+        with:
+          fetch-depth: 0
+
+      - name: Setup Bun
+        uses: oven-sh/setup-bun@v2
+        with:
+          bun-version: latest
+
+      - name: Install dependencies
+        run: bun install
+
+      - name: Run tests
+        run: bun test
+
+      - name: Check version change
+        id: check_version
+        run: |
+          VERSION=v$(cat package.json | jq -r .version)
+          if git rev-parse "$VERSION" >/dev/null 2>&1; then
+            echo "CHANGED=false" >> $GITHUB_OUTPUT
+            echo "Skipping release: Version $VERSION already released."
+          else
+            echo "CHANGED=true" >> $GITHUB_OUTPUT
+            echo "VERSION=$VERSION" >> $GITHUB_OUTPUT
+            echo "Found new version: $VERSION"
+          fi
+
+      - name: Push Tag
+        if: steps.check_version.outputs.CHANGED == 'true'
+        run: |
+          git config user.name "github-actions"
+          git config user.email "github-actions@github.com"
+          git tag ${{ steps.check_version.outputs.VERSION }}
+          git push origin ${{ steps.check_version.outputs.VERSION }}
+
+      - name: Create GitHub Release
+        if: steps.check_version.outputs.CHANGED == 'true'
+        uses: softprops/action-gh-release@v1
+        with:
+          tag_name: ${{ steps.check_version.outputs.VERSION }}
+          generate_release_notes: true
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+
+      - name: Publish to NPM
+        if: steps.check_version.outputs.CHANGED == 'true'
+        run: |
+          echo "//registry.npmjs.org/:_authToken=${NPM_TOKEN}" > .npmrc
+          bun run build # (if any build steps were needed, currently we use bun/ts directly)
+          npm publish --access public
+        env:
+          NPM_TOKEN: ${{ secrets.NPM_TOKEN }}

package/.husky/pre-commit

@@ -0,0 +1 @@
+bun run lint

package/.nvmrc

@@ -0,0 +1 @@
+24

package/CHANGELOG.md

@@ -0,0 +1,29 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [0.2.2] - 2026-03-19
+
+- OSS release
+- Added GitHub Actions for CI/CD and Releases.
+- Added `CONTRIBUTING.md`, Code of Conduct, and Security Policy.
+- Added status badges to `README.md`.
+
+## [0.2.1] - 2026-03-19
+
+- Improved diagnostic messages to be more actionable.
+- Updated OpenRouter, Model Suffix, Telemetry, and Connectivity rules.
+
+## [0.2.0] - 2026-03-19
+
+- Initial stable CLI configuration.
+- Basic health check implementation.
+- `check`, `fix`, and `init` commands.
+
+## [0.1.0] - 2026-03-19
+
+- Prototype of Claude Config Doctor.
+- Basic schema validation.

package/CLAUDE.md

@@ -0,0 +1,106 @@
+
+Default to using Bun instead of Node.js.
+
+- Use `bun <file>` instead of `node <file>` or `ts-node <file>`
+- Use `bun test` instead of `jest` or `vitest`
+- Use `bun build <file.html|file.ts|file.css>` instead of `webpack` or `esbuild`
+- Use `bun install` instead of `npm install` or `yarn install` or `pnpm install`
+- Use `bun run <script>` instead of `npm run <script>` or `yarn run <script>` or `pnpm run <script>`
+- Use `bunx <package> <command>` instead of `npx <package> <command>`
+- Bun automatically loads .env, so don't use dotenv.
+
+## APIs
+
+- `Bun.serve()` supports WebSockets, HTTPS, and routes. Don't use `express`.
+- `bun:sqlite` for SQLite. Don't use `better-sqlite3`.
+- `Bun.redis` for Redis. Don't use `ioredis`.
+- `Bun.sql` for Postgres. Don't use `pg` or `postgres.js`.
+- `WebSocket` is built-in. Don't use `ws`.
+- Prefer `Bun.file` over `node:fs`'s readFile/writeFile
+- Bun.$`ls` instead of execa.
+
+## Testing
+
+Use `bun test` to run tests.
+
+```ts#index.test.ts
+import { test, expect } from "bun:test";
+
+test("hello world", () => {
+  expect(1).toBe(1);
+});
+```
+
+## Frontend
+
+Use HTML imports with `Bun.serve()`. Don't use `vite`. HTML imports fully support React, CSS, Tailwind.
+
+Server:
+
+```ts#index.ts
+import index from "./index.html"
+
+Bun.serve({
+  routes: {
+    "/": index,
+    "/api/users/:id": {
+      GET: (req) => {
+        return new Response(JSON.stringify({ id: req.params.id }));
+      },
+    },
+  },
+  // optional websocket support
+  websocket: {
+    open: (ws) => {
+      ws.send("Hello, world!");
+    },
+    message: (ws, message) => {
+      ws.send(message);
+    },
+    close: (ws) => {
+      // handle close
+    }
+  },
+  development: {
+    hmr: true,
+    console: true,
+  }
+})
+```
+
+HTML files can import .tsx, .jsx or .js files directly and Bun's bundler will transpile & bundle automatically. `<link>` tags can point to stylesheets and Bun's CSS bundler will bundle.
+
+```html#index.html
+<html>
+  <body>
+    <h1>Hello, world!</h1>
+    <script type="module" src="./frontend.tsx"></script>
+  </body>
+</html>
+```
+
+With the following `frontend.tsx`:
+
+```tsx#frontend.tsx
+import React from "react";
+import { createRoot } from "react-dom/client";
+
+// import .css files directly and it works
+import './index.css';
+
+const root = createRoot(document.body);
+
+export default function Frontend() {
+  return <h1>Hello, world!</h1>;
+}
+
+root.render(<Frontend />);
+```
+
+Then, run index.ts
+
+```sh
+bun --hot ./index.ts
+```
+
+For more information, read the Bun API docs in `node_modules/bun-types/docs/**.mdx`.

package/CONTRIBUTING.md

@@ -0,0 +1,73 @@
+# Contributing to Claude Config Doctor 🩺
+
+First off, thank you for considering contributing to Claude Config Doctor! It's people like you that make Claude Config Doctor such a great tool.
+
+## Code of Conduct
+
+By participating in this project, you are expected to uphold our [Code of Conduct](.github/CODE_OF_CONDUCT.md).
+
+## How Can I Contribute?
+
+### Reporting Bugs
+
+- **Search first**. Before creating a new issue, please check if the bug has already been reported.
+- **Provide details**. If you find a bug, please create an issue with a clear description of the problem, expected behavior, and steps to reproduce.
+- **Environment info**. Mention your OS, Node.js/Bun version, and any relevant configuration snippets (redact sensitive information like API keys!).
+
+### Suggesting Enhancements
+
+- **Open an issue**. Describe the feature you'd like to see and why it would be useful.
+- **Provide context**. How does this solve a problem for users of Claude Code?
+
+### Pull Requests
+
+1. **Check for existing issues**. If you're planning a major change, it's best to open an issue for discussion first.
+2. **Fork the repo** and create your branch from `main`.
+3. **Install dependencies**: `bun install`.
+4. **Make your changes**. Write clean, documented code.
+5. **Lint and Format**: Run `bun run lint` to ensure your code matches the style. Biome will automatically check for common issues.
+6. **Run tests**: `bun test`. Ensure all tests pass before submitting.
+7. **Submit PR**. Provide a clear description of your changes and link to any related issues.
+
+## Development Setup
+
+To set up the development environment, you will need:
+- [Bun](https://bun.sh/) installed.
+- [Biome](https://biomejs.dev/) (installed via dependencies).
+- Any modern code editor (VS Code recommended with the Biome extension).
+
+```bash
+# Clone the repository
+git clone https://github.com/mirogta/claude-config-doctor.git
+cd claude-config-doctor
+
+# Install dependencies
+bun install
+
+# Lint and Format
+bun run lint
+bun run format
+
+# Run tests
+bun test
+```
+
+## Commit Message Guidelines
+
+We follow the [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) specification for our commit messages. This helps us generate clean and automated changelogs.
+
+Format: `<type>(<scope>): <description>`
+
+Common types:
+
+- `feat`: A new feature
+- `fix`: A bug fix
+- `docs`: Documentation only changes
+- `style`: Changes that do not affect the meaning of the code (white-space, formatting, etc)
+- `refactor`: A code change that neither fixes a bug nor adds a feature
+- `test`: Adding missing tests or correcting existing tests
+- `chore`: Changes to the build process or auxiliary tools and libraries
+
+## License
+
+By contributing, you agree that your contributions will be licensed under the [MIT License](LICENSE).

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 mirogta
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -0,0 +1,44 @@
+# Claude Config Doctor 🩺
+
+[![CI Status](https://github.com/mirogta/claude-config-doctor/actions/workflows/ci.yml/badge.svg)](https://github.com/mirogta/claude-config-doctor/actions)
+[![License: MIT](https://img.shields.io/github/license/mirogta/claude-config-doctor)](LICENSE)
+[![npm version](https://img.shields.io/npm/v/claude-config-doctor)](https://www.npmjs.com/package/claude-config-doctor)
+
+An **extra diagnostic tool** designed specifically to find and fix common community-reported pitfalls in Claude Code configuration files. It acts as a specialized extension to the built-in Claude doctor.
+
+## 🚀 Usage
+
+Run the doctor instantly with `npx` in either your repo root or home directory:
+
+```bash
+# Check for common configuration issues
+npx claude-config-doctor check
+
+# Apply autofixes for known model-naming and API key conflicts
+npx claude-config-doctor fix
+
+# Initialize a fresh repo-level config template
+npx claude-config-doctor init
+```
+
+## 🔍 Targeted Diagnostics
+
+The Doctor focuses on some specific frustration points:
+
+- ✅ **Schema Guard**: Validates your configuration against official JSON standards.
+- ✅ **OpenRouter Bridge Verification**: Ensures correct variable separation for OpenRouter integrations.
+- ✅ **Model Name Errors**: Detects and strips accidental `:free` suffixes that cause "Model not found" errors.
+
+## 🛠️ Pro Workflow
+
+The tool automatically prioritizes `./.claude/settings.local.json` but checks `~/.claude/settings.json` too.
+
+```bash
+# Output raw results for scriptable diagnostics or CI/CD
+npx claude-config-doctor check --json
+```
+
+## 📜 License
+
+MIT.
+For more information, please read our [Contributing Guide](CONTRIBUTING.md).

package/SECURITY.md

@@ -0,0 +1,24 @@
+# Security Policy
+
+## Supported Versions
+
+Currently, only the latest version of Claude Config Doctor is supported for security updates.
+
+| Version | Supported          |
+| ------- | ------------------ |
+| latest  | :white_check_mark: |
+
+## Reporting a Vulnerability
+
+If you discover a potential security vulnerability in this project, please **do not open a public issue**. Instead, please report it by opening a private security advisory on GitHub or by contacting the maintainer directly via GitHub.
+
+We will acknowledge your report and work with you to understand and resolve the issue.
+
+Please include the following information in your report:
+
+-   A description of the vulnerability.
+-   The potential impact of the vulnerability.
+-   Steps to reproduce the vulnerability (if known).
+-   Your recommended fix or mitigation (if known).
+
+Thank you for helping keep this project secure!

package/bin/cli.js

@@ -0,0 +1,108 @@
+#!/usr/bin/env node
+import fs from 'node:fs';
+import os from 'node:os';
+import path from 'node:path';
+import chalk from 'chalk';
+import yargs from 'yargs';
+import { hideBin } from 'yargs/helpers';
+import { checkConfig, fixConfig, initConfigWizard } from '../lib/healthcheck.js';
+
+const DEFAULT_LOCAL = path.join(process.cwd(), '.claude/settings.local.json');
+const DEFAULT_GLOBAL = path.join(os.homedir(), '.claude/settings.json');
+
+const parser = yargs(hideBin(process.argv))
+  .scriptName('claude-config-doctor')
+  .usage('$0 <command> [options]')
+  .command(['check [file]', '$0 [file]'], 'Run diagnostics on Claude settings (default)', (y) => {
+    y.positional('file', { describe: 'Path to config file', type: 'string' });
+  })
+  .command('fix [file]', 'Apply autofixes for known model and API issues', (y) => {
+    y.positional('file', { describe: 'Path to config file', type: 'string' });
+  })
+  .command('init [file]', 'Initialize a new config template', (y) => {
+    y.positional('file', { describe: 'Path to create config', type: 'string' });
+  })
+  .option('json', { type: 'boolean', describe: 'Output raw JSON results', global: true })
+  .help();
+
+const argv = parser.parseSync();
+
+async function showReport(filePath, result) {
+  console.log(chalk.bold(`\n🩺 Diagnostic Report (Extra): ${chalk.cyan(filePath)}`));
+  if (result.issues.length === 0) {
+    console.log(`  ${chalk.green('✓')} No issues detected by the Doctor.`);
+    return;
+  }
+
+  result.issues.forEach((issue) => {
+    let icon = chalk.red('✖');
+    let color = chalk.red;
+    if (issue.type === 'telemetry') {
+      icon = chalk.yellow('⚠');
+      color = chalk.yellow;
+    }
+    if (issue.type === 'model_suffix') {
+      icon = chalk.blue('🩹');
+      color = chalk.blue;
+    }
+    if (issue.type === 'connectivity') {
+      icon = chalk.yellow('☁');
+      color = chalk.yellow;
+    }
+    if (issue.type === 'api_key') {
+      icon = chalk.red('🔐');
+      color = chalk.red;
+    }
+    if (issue.type === 'read_error') {
+      icon = chalk.red('🚫');
+      color = chalk.red;
+    }
+    if (issue.type === 'gitignore') {
+      icon = chalk.yellow('🪵');
+      color = chalk.yellow;
+    }
+
+    console.log(`  ${icon} ${color(issue.message)}`);
+  });
+}
+
+(async () => {
+  const cmd = argv._[0] || 'check';
+
+  if (cmd === 'init') {
+    const file = path.resolve(argv.file || DEFAULT_LOCAL);
+    const result = await initConfigWizard(file);
+    if (result.success) console.log(chalk.green(`\n✨ Template @ ${chalk.cyan(result.filePath)}`));
+    return;
+  }
+
+  const filesToCheck = [];
+  if (argv.file) {
+    filesToCheck.push(path.resolve(argv.file));
+  } else {
+    if (fs.existsSync(DEFAULT_LOCAL)) filesToCheck.push(DEFAULT_LOCAL);
+    if (fs.existsSync(DEFAULT_GLOBAL)) filesToCheck.push(DEFAULT_GLOBAL);
+  }
+
+  if (filesToCheck.length === 0) {
+    console.log(chalk.red(`\n✖ No config files found in standard locations.`));
+    process.exit(1);
+  }
+
+  let hasIssues = false;
+  for (const file of filesToCheck) {
+    const result = cmd === 'fix' ? await fixConfig(file) : await checkConfig(file);
+    if (result.issues.length > 0) hasIssues = true;
+
+    if (argv.json) {
+      console.log(JSON.stringify({ file, ...result }, null, 2));
+    } else {
+      await showReport(file, result);
+      if (cmd === 'fix' && result.fixed) {
+        console.log(chalk.green(`  ${chalk.bold('✔')} Auto-fixes applied successfully.`));
+      }
+    }
+  }
+
+  if (cmd !== 'fix' && hasIssues) process.exit(1);
+})();

package/biome.json

@@ -0,0 +1,27 @@
+{
+  "$schema": "https://biomejs.dev/schemas/2.4.3/schema.json",
+  "vcs": {
+    "enabled": true,
+    "clientKind": "git",
+    "useIgnoreFile": true
+  },
+  "formatter": {
+    "enabled": true,
+    "indentStyle": "space",
+    "indentWidth": 2,
+    "lineWidth": 100
+  },
+  "linter": {
+    "enabled": true,
+    "rules": {
+      "recommended": true
+    }
+  },
+  "javascript": {
+    "formatter": {
+      "quoteStyle": "single",
+      "semicolons": "always",
+      "trailingCommas": "es5"
+    }
+  }
+}