aix-doctor

Pre-submit review for the AiX marketplace. Run the exact same checks AiX runs server-side, locally, before you submit.

Why

If aix-doctor says you're green, the post-submit pipeline says the same. Same code path (@aix/review-core), same verdicts. Stop flying blind into review.

Install

npm i -g @aixstore/aix-doctor
# or one-off:
npx @aixstore/aix-doctor simulate

Two ways to use

1. CLI (fastest)

cd /path/to/your/repo
aix-doctor simulate         # runs every check, prints a report

Exit code 0 = green or amber, 1 = red.

2. MCP server (in Claude Code / Cursor / any MCP client)

aix-doctor                  # starts the MCP server on stdio

Add to your client's MCP config (Claude Code: ~/.claude/mcp_settings.json):

{
  "mcpServers": {
    "aix-doctor": { "command": "aix-doctor" }
  }
}

Tools exposed:

| Tool | What | |---|---| | aix.check_structure | README / spec / manifest / icon / screenshots present? | | aix.validate_spec | Same Zod validator AiX uses on aix.deploy.yaml | | aix.review_security | Secret leaks, raw pg, hand-rolled auth, SDK pinning | | aix.review_db_migration | Migration plan to @aix/db-adapter | | aix.review_sso | Migration plan to @aix/auth-sdk | | aix.review_yaml_pipeline | Build/runtime/aix_auth block sanity | | aix.simulate_review | All of the above, end-to-end. Returns green | amber | red | | aix.scaffold_plan | Plan files to create — returns diff only, no writes | | aix.scaffold_apply | Apply a confirmed scaffold plan |

Consent model

Mutations always require consent. aix.scaffold_plan returns the file list and bodies it would write; the client (Claude Code, Cursor, etc) is expected to show this to you and only call aix.scaffold_apply after you say yes. The default behavior of every MCP-aware coding agent is to do exactly that.

By contrast, the post-submit AiX pipeline auto-merges fixes — but those land in our mirror of your repo, not your source. Two different copies, two different policies.

License

MIT.