nmindz/stupid-comments

Runtime enforcement for a code comment policy: a Rust CLI plus a DeepSeek Harness adapter that refuses a write when it violates your own prose rules.

stupid-comments is runtime enforcement for a code-comment policy: it parses what a model is about to write, checks it against your policy, and refuses the write when it violates. The README explains the enforcement is moved out of the prompt and into the runtime, re-injecting your policy text verbatim at the moment it matters, and that the policy is never baked in. The engine runs as one binary across every harness — DSH wires it through tools/pre-execute, agent/turn-stopping and subagent/end. The README documents layered gates (a pre-write gate and a stop gate that diffs the working tree), classification of comments into directive / license-header / doc-comment / prose, git-anchored suppression pragmas that only count if the identical line is already in HEAD, an evasion detector for files that lost their comments, and default shadow mode where findings are reported but nothing is blocked.

Coding & Development ★ 0
View on GitHub ↗

Install

dsh plugin --profile tui add github:nmindz/stupid-comments

Copied verbatim from the README's 'for DeepSeek Harness' line inside the Quick start (the README also shows a checkout form, dsh plugin --profile tui add /path/to/clone). The README notes the package declares a dsh.bundle patch, so dsh plugin add installs and reconciles it into that profile's bundle list on its own; the CLI binary must also be installed separately and resolvable on PATH, or the plugin reports a missing binary and enforces nothing.

Compatibility

The README's Installation section requires a Rust toolchain for the CLI half and says the plugin never downloads or executes anything on your behalf. It says the DSH adapter targets DSH 0.2.x, with the range declared through optional @deepseek-ai/dsh-* peer dependencies (a dsh outside the range refuses the install until you grant dsh plugin allow-version, and the 0.2 line matters because its session format refuses the retired plugin source kind). Policy is read from a # Comments Policy section of your agent memory (~/.dsh/AGENTS.md for DSH) or a .stupid-comments.jsonc; with no policy it stays completely silent.

Details

FAQ

Does it block writes out of the box?
No. The README says mode defaults to shadow (findings reported, nothing blocked) and advises staying there until the log convinces you the blocks would have been right; only then set mode to block.
Can the model disable the gate itself?
No. The README says the only mid-session escape hatch is STUPID_COMMENTS=0 in the session environment, which lives somewhere the model cannot write, and suppression pragmas are honoured only if the identical line already exists in HEAD.

Alternatives

030611/dsh-context-provenance · 030611/qiushi-dsh-evidence-audit · 1001WillsStudio/AuroraCoder

More plugins in Coding & Development

Browse more in Coding & Development

Guides for Coding & Development plugins