docs: require exhaustive MCP-server use in project memory#120
Conversation
Add a standing directive to the Local MCP/tooling section of CLAUDE.md and mirror it identically to AGENTS.md: the MCP servers are the primary engineering surface for QSL and must be used exhaustively for every substantive task (codescene gate before PRs, git/github for review, qsl-results for benchmark history, codex for second-opinion review, context7 for any library API, sequential-thinking, filesystem, docker), preferring the dedicated MCP over ad-hoc shell. Also document the four newly configured servers (codex, git, github, qsl-results). Keeps the two memory files in agreement per the repo's sync rule.
There was a problem hiding this comment.
No application code in the PR — skipped Code Health checks.
See analysis details in CodeScene
Quality Gate Profile: Pay Down Tech Debt
Install CodeScene MCP: safeguard and uplift AI-generated code. Catch issues early with our IDE extension and CLI tool.
|
Caution Review failedPull request was closed or merged during review 📝 WalkthroughWalkthroughBoth ChangesMCP Tooling Documentation
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Poem
🚥 Pre-merge checks | ✅ 4✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 93fcfff39a
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Address PR #120 review: - HANDOFF.md said 'use GitHub CLI over GitHub MCP', contradicting the new MCP-first directive (and resume reads HANDOFF after CLAUDE/AGENTS). Flip HANDOFF to one canonical workflow: prefer the GitHub MCP for PR/issue/branch/commit/milestone review, gh CLI as fallback when the MCP is unavailable or for scripted steps; likewise prefer context7 for current docs over memory. - The directive named 'sequential-thinking' (hyphen) while the roster and HANDOFF use 'sequential_thinking' (underscore); standardize on the configured underscore name in CLAUDE.md and AGENTS.md so no line points at an unconfigured server name.
) Address PR #120 review: - HANDOFF.md said 'use GitHub CLI over GitHub MCP', contradicting the new MCP-first directive (and resume reads HANDOFF after CLAUDE/AGENTS). Flip HANDOFF to one canonical workflow: prefer the GitHub MCP for PR/issue/branch/commit/milestone review, gh CLI as fallback when the MCP is unavailable or for scripted steps; likewise prefer context7 for current docs over memory. - The directive named 'sequential-thinking' (hyphen) while the roster and HANDOFF use 'sequential_thinking' (underscore); standardize on the configured underscore name in CLAUDE.md and AGENTS.md so no line points at an unconfigured server name.
Summary
Adds a standing directive to the
Local MCP/tooling memorysection ofCLAUDE.mdand mirrors it identically intoAGENTS.md: the configured MCP servers are the primary engineering surface for QSL and must be used exhaustively for every substantive task, rather than falling back to ad-hoc shell.Task → server mapping made explicit:
codescenereview +analyze_change_setgate before PRs;git/githubfor diffs/blame/history and PR/issue/branch/commit/milestone review;qsl-results(SQLite) for benchmark history;codexfor second-opinion review before finishing a milestone;context7for current library docs;sequential-thinking,filesystem,docker. Practical guard kept: prefer the dedicated MCP, skip a server only when it genuinely cannot do the step (e.g. destructivegit pushstays manual per the golden rules); never invent an unconfigured server.Also documents the four newly configured servers:
codex,git,github,qsl-results.Why a separate branch
This is a project-memory/policy change, unrelated to the in-flight M47 storage PR (#119), so it gets its own branch/PR to keep #119 scoped — matching the repo's precedent for memory-sync PRs.
Definition of Done
Claude Code clientvsCodex clientheader line)Notes
githubMCP needs a one-time OAuth via/mcp;ghCLI remains the working fallback. Servers were installed at user scope (machine-local), so this PR only records the policy and roster in shared project memory.Summary by CodeRabbit