dsh-fix-verify: Verify Whether Fixes Landed with DeepSeek Harness

What Does It Do?

Fix Verify is a DSH plugin for DeepSeek Harness that answers whether the issues reported before a change are actually gone after it. Instead of adding new detection rules, it reuses the rules from the guard plugins you already have installed and runs the exact same rule set against a before snapshot and an after snapshot of your code. It then compares results by rule ID plus file-relative path and sorts them into fixed, remaining, new regression, and new file buckets. Maintained by feely0208 under the MIT license and written in JavaScript, it turns remediation review into a checkable before-and-after comparison.

Core Features

• Same-rules comparison: runs an identical rule set against the before and after directories and reports fixed, remaining, new regression, and new file buckets.
• Rule ID plus relative path as the comparison key: line numbers are deliberately excluded, so adding a comment cannot shift lines and make an unfixed issue look fixed.
• Automatic rule discovery: finds rules from a specified directory, installed guard plugins, side-by-side installs, and an environment variable, labeling each source by plugin short name.
• Fails on empty rule sources: exits with code 2 when no rule source is found, never reporting an unchecked run as zero hits.
• Multiple output forms: a quiet conclusion-only mode, JSON output for downstream compliance documents, and an optional Markdown review report for archiving.
• Exit codes as a gate: 0 means no remaining issues and no regressions, 1 means issues remain, 2 means bad arguments or no rule source found.

How to Use This Plugin?

After enabling it in DSH, prepare two snapshots of your code and let the plugin run the same rules over both. The cleanest way to get a before snapshot is a git worktree checked out at the previous commit; you can also export an old commit into a temporary directory, or simply point it at two ordinary directories since a git repository is not required. The common call passes both the before and after directories. For CI, use the quiet mode to print only the conclusion line; for deliverables, emit JSON and hand it to the compliance document plugin; for archival, add the Markdown review report. Gate scripts can pass a single directory as both before and after, and rule sources can be pointed at a directory containing several guard plugin rule sets. Remember it is a comparator, not a scanner: zero remaining issues only means the current rule set reported nothing on these two snapshots, and no hit does not prove the project is clean.

How to Troubleshoot This Plugin?

Exit code 2 means bad arguments, a missing directory, or no rule source discovered, and such a run does not count as a pass. First confirm the before and after paths really exist, then check whether the guard plugins are installed or point the rule-source option at the plugin directory explicitly; the plugin lists the plugins it found and explains how to specify a rule source. If the output shows an empty rule source, do not trust any all-fixed conclusion — restore the rule sources as the official instructions describe and run the review again.