AI Agent Hub
Back to plugins
🧩

review-gate

admin-security Updated 2026.08.25

Run the following command in DeepSeek Harness:

dsh plugin install JohnXu22786/review-gate

Paste the following prompt into your AI chat to install this plugin:

Run dsh plugin install JohnXu22786/review-gate in the DeepSeek Harness terminal to install this plugin; the full source-code repository is https://github.com/JohnXu22786/review-gate .

About this plugin

Most code-review plugins in the ecosystem stop at annotating a diff; none of them actually block a bad merge from proceeding. review-gate closes that gap by turning review into a hard gate: a merge is only unlocked after deterministic rule checks and a team approval quorum are both satisfied. Findings are graded severe, warning, and suggestion, produced by built-in static rules (leftover TODOs, debugger statements, console logs, hardcoded secrets, and more) and optionally enriched by an LLM. The model can only add findings; it can never bypass a threshold.

The pass/fail verdict is a pure function of persisted state - fully reproducible and free of model judgment. Team approval supports a configurable quorum, and a re-review invalidates stale approvals and acknowledgements. Every run, vote, acknowledgement, and export is appended to an immutable audit log, exportable as a JSON or Markdown compliance report. All tools and CLI commands emit machine-readable JSON with correct exit codes, ready for GitHub Actions, pre-commit hooks, or branch-protection policies.

Ideal for teams that treat merge quality as a hard requirement - regulated industries such as finance, healthcare, or security-critical projects that need an auditable compliance trail, and engineering organizations that want CI to automatically block low-quality pull requests. Individual developers can likewise upgrade review from a polite suggestion to an enforceable checkpoint, leaving a traceable record of every merge decision.

Use Cases

  • Automatically block unapproved merges in GitHub Actions or branch-protection policies
  • Enforce a team approval quorum before any merge in regulated finance or healthcare repositories
  • Turn past failure findings into reusable static rules to continuously reduce missed issues

Best For

  • Engineering team leads and security-sensitive project owners who treat merge quality as a hard requirement
  • Compliance and risk teams that need a traceable, immutable audit trail for every merge decision
  • DevOps engineers building CI pipelines who want deterministic exit codes to drive merge-gate logic