Skip to content

fix: setup skip output, --force flag, npx mcp entry#76

Closed
George-iam wants to merge 1 commit intomainfrom
fix/setup-skip-output-20260408
Closed

fix: setup skip output, --force flag, npx mcp entry#76
George-iam wants to merge 1 commit intomainfrom
fix/setup-skip-output-20260408

Conversation

@George-iam
Copy link
Copy Markdown
Contributor

Summary

Three fixes for setup flow:

  1. Skip output: when setup runs on already-initialized project, now shows:

    Already initialized (skipped LLM scan). Use --force to re-scan.
    Decisions: 104, Memories: 15
    

    Instead of misleading "Oracle: 4 files (LLM scan)" when no scan happened.

  2. --force flag: axme-code setup --force re-runs LLM scan even if already initialized.

  3. npx mcp entry: setup was hardcoding command: "axme-code" in .mcp.json, overwriting the npx format from PR feat: switch to npx for plugin marketplace compatibility #75. Now writes command: "npx", args: ["-y", "@axme/code", "serve"].

Test plan

🤖 Generated with Claude Code

- Setup on already-initialized project shows "Already initialized
  (skipped LLM scan). Use --force to re-scan." instead of misleading
  LLM scan counts
- Added --force flag to force re-run LLM scan
- Fixed hardcoded mcp entry in setup: was "axme-code serve", now
  "npx -y @axme/code serve" — setup was overwriting the npx format

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@George-iam
Copy link
Copy Markdown
Contributor Author

Superseded by #77 which includes all these changes plus npx revert and CI workflow.

@George-iam George-iam closed this Apr 8, 2026
@George-iam George-iam deleted the fix/setup-skip-output-20260408 branch April 8, 2026 13:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant