You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We find that combining Our Friend (which is what we call Claude 3.5 sonnet v2) with linters sorts out a lot of the weird issues that are sometime introduced when getting Claude to work on a large codebase.
We make heavy and automated use of -fix aligned to a set of linting and formatting rules for typescript and python and it works crazy well, giving Claude the ability to consistently interact with and build huge, complex codebases in a way we've just not seen from the other LLM's.
I think (somehow) baking in:
eslint
ruff
Prettier
... makes a lot of sense, but I'm not familiar enough with MCP yet to make a meaningful suggestion on how to do it.
The work this issue asked for is now scoped in #4864: a root Prettier config and ESLint flat config shared across the TypeScript workspaces, a root npm run validate, and CI running it. That issue is part of the agentic software factory tracker #4858.
Thank you for the suggestion, and apologies for the long wait for a response.
The reference servers were rebuilt for the 2026-07-28 MCP specification (#4857) and released as v2 (2.0.0 on npm for the TypeScript servers, 2026.10.19 on PyPI for the Python servers), and what this asks for is covered there. The repository now has a shared ESLint flat config and Prettier formatting, enforced by npm run validate and the pre-push gate in CI. This is happening as part of the backlog triage in #4875.
If the v2 behavior doesn't meet the need you had in mind, please open a fresh issue describing what's still missing; see CONTRIBUTING.md.
Activity
davidmoore-io commentedon Dec 3, 2024
+1 on this.
We find that combining Our Friend (which is what we call Claude 3.5 sonnet v2) with linters sorts out a lot of the weird issues that are sometime introduced when getting Claude to work on a large codebase.
We make heavy and automated use of
-fixaligned to a set of linting and formatting rules for typescript and python and it works crazy well, giving Claude the ability to consistently interact with and build huge, complex codebases in a way we've just not seen from the other LLM's.I think (somehow) baking in:
... makes a lot of sense, but I'm not familiar enough with MCP yet to make a meaningful suggestion on how to do it.
jspahrsummers commentedon Dec 3, 2024
Ah, sorry, this was specifically with the
serversrepo in mind—so when folks make PRs here, we don't get a bunch of noisy formatting changes 😄If you're thinking there should be some broader MCP + linting/formatting thing, would love to discuss!
cliffhall commentedon Sep 27, 2026
The work this issue asked for is now scoped in #4864: a root Prettier config and ESLint flat config shared across the TypeScript workspaces, a root
npm run validate, and CI running it. That issue is part of the agentic software factory tracker #4858.cliffhall commentedon Oct 19, 2026
Closing: this is available in the v2 release.
Thank you for the suggestion, and apologies for the long wait for a response.
The reference servers were rebuilt for the 2026-07-28 MCP specification (#4857) and released as v2 (2.0.0 on npm for the TypeScript servers, 2026.10.19 on PyPI for the Python servers), and what this asks for is covered there. The repository now has a shared ESLint flat config and Prettier formatting, enforced by npm run validate and the pre-push gate in CI. This is happening as part of the backlog triage in #4875.
If the v2 behavior doesn't meet the need you had in mind, please open a fresh issue describing what's still missing; see
CONTRIBUTING.md.