wtf is storybook-oversight?

Oversight is a tool for developers who use AI coding agents alongside Storybook, the popular tool for building and documenting user interface components. When a coding agent looks at your components, it does not read your source code directly. Instead it reads a manifest file that Storybook's MCP server generates, a kind of summary of what each component does. The problem this project solves is that sometimes a component's description never makes it into that manifest, because the extraction process failed, the wrong tool ran, or the documentation comments were missing in the first place. When that happens, the agent sees a component with no description and nothing warns you that this happened. Oversight checks that manifest for each component and flags the gaps, either while you are actively working in Storybook or automatically during continuous integration checks before code is merged. The actual checking rules live in one shared core package so that both the interactive version and the automated version always agree on what counts as a problem. There are two ways to use it. The Storybook addon adds a panel to every component story and an inline block on the documentation page, so you see issues while you work. The command line tool, called oversight, checks the manifest during your CI pipeline and fails the build if a change breaks or removes a component's documentation. The project is organized as a set of packages: a core package holding the diagnostic rules as plain functions, the Storybook addon itself, and the command line linter. There is also a demo Storybook included that showcases components deliberately built to trigger each rule, so you can see the tool in action. To develop the project, you install dependencies with pnpm, then use commands to build every package, run tests, check linting, and build or run the demo Storybook locally. The project is released under the MIT license, a permissive license that allows free use, modification, and distribution.