dsh-plugin-noema: A Code Complexity Review Plugin for DeepSeek Harness

What Does It Do?

Noema is a DSH plugin for DeepSeek Harness that reviews code complexity changes after each coding task. It solves the problem of not knowing which files and functions became harder to follow during AI-assisted development, so you can focus review effort where it matters. Analysis runs locally, comparing the workspace at the start and end of every turn, and the results stay outside the model context.

Core Features

• Three complexity metrics compared: cyclomatic complexity, cognitive complexity, and maximum nesting depth are reported before and after each task, covering independent paths, control-flow difficulty, and nesting levels.
• File and function drill-down: expand a file or function to locate changes inside it, with [Top Level] showing top-level code separately from named child functions and unchanged code hidden by default.
• Local, context-safe analysis: metrics are computed locally against the workspace at the start and end of each turn, including manual edits made in between, and never enter the model context.
• Defined language support: TypeScript (including TSX), Python, and Go are analyzed, while JavaScript and TypeScript declaration files are excluded.
• Quiet when nothing changed: no card appears when there are no supported code changes, including comment-only or formatting edits, though code changes still show when scores stay the same.
• Configurable file scope: include and exclude patterns are relative to the workspace, exclusions take precedence, and .gitignore plus common dependency and build directories are respected by default.

How to Use This Plugin?

After enabling it in DSH, simply ask DSH to modify a supported source file and the complexity change card appears at the end of the turn. To narrow or widen the scope, open Plugins → plugin-noema → Files to analyze in the Web sidebar, set include and exclude patterns relative to your workspace (such as src/** or **/*.test.ts), or use Add common test exclusions; saved changes apply from the next turn. If DSH is already running, restart it and refresh the browser so the plugin begins analyzing new turns.

How to Troubleshoot This Plugin?

If no complexity card appears, first check whether the turn actually changed supported source code: comment-only or formatting edits, and changes confined to JavaScript or TypeScript declaration files, produce no card. Right after enabling the plugin, restart DSH and refresh the browser, since it only analyzes turns that happen after installation. If specific files are missing from the analysis, review the exclude patterns in Files to analyze, because exclusions take precedence over includes.