DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to trace why an approval was allowed or denied with DSH Auto Review

Rebuild each AI approval decision from the session log to check what the reviewer did.

Who it is forA team lead or security-minded developer who needs to explain or review an approval that an AI reviewer allowed or denied.

The problemWhen an agent action is approved or blocked automatically, it is hard to tell which evidence and which rule produced the decision.

The outcomeThe reviewer's decision is traced from the session log through the events approval/asked, autoReview/verdict or autoReview/rejection, and approval/decided, with the reason attached.

What you need first

  • DeepSeek Harness (dsh) installed, with a profile named web or another profile of your choice
  • Harness version compatible with the plugin (the README lists dsh-v0.2.1-rc.2 as verified)
  • Network access to install from GitHub or npm
  • pnpm, only if you use the tarball channel or need to approve native build scripts

Steps

  1. Install the plugin if it is not present: dsh plugin --profile web add dsh-auto-review
  2. Run /auto-review status in the session to see recent verdicts and fallbacks
  3. Open the session log and find the approval/asked event for the request you want to check
  4. Follow the chain to the matching autoReview/verdict or autoReview/rejection event, then to approval/decided
  5. Read the reviewer reason and riskLevel in the verdict and confirm the final decision matches it

Prompt for your agent

Using the repo PerryLink/dsh-auto-review, locate in the session log of <session-id> the approval/asked event for the request named <request-id>, then follow it to the autoReview/verdict or autoReview/rejection event and the approval/decided event. Report the decision, the reviewer reason, and the riskLevel. Verify that the final approval/decided outcome matches the verdict, and flag any mismatch.

Caveat. The audit chain depends on the session log keeping these events, and the README notes that allowUnmarkedAudit changes how hosts handle unmarked events, so check that setting before relying on the log.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page