coderaiser / putout-editor / 36324969805

100%

push

github

feature: mcp: docs gets a style section, so the conventions are one call away

An agent writing a plugin had get_example for the four patterns and nothing for the
conventions around them. get_example is a proxy - it teaches a shape, not a package - and
the shape it teaches is not where these repos go wrong. The mistakes are elsewhere:
importing from a sibling plugin instead of from putout, writing an index.js for a
single-rule plugin, and shipping a fixture without its fixed twin.

docs {section: 'style'} answers those, in the order an agent makes them. Condensed on
purpose: the full guide is docs/putout-style.md in this repository, and examples.ts
already records what happens when a copy of a shipped rule is kept instead of read - the
markdown one drifted and taught a rule nobody runs. This keeps the four conventions
rather than the statistics, and points at the file for the numbers, so a count going stale
does not make the section wrong.

Six specs pin it: the section is in the enum, the overview advertises it, it says
peerDependency, it names both package shapes, and it points at the full guide. That last
one is the anti-drift pin - if the doc moves, the section fails rather than lying about
where to look.

148 tests, 100% coverage.

1081 of 1081 branches covered (100.0%)

Branch coverage included in aggregate %.

6663 of 6663 relevant lines covered (100.0%)

61.54 hits per line