---
name: review-coding-agent-command-logs-for-risky
description: "Flag and summarize shell commands an agent ran, ready for human review. Each day the bot reads the command history left behind by an automated coding agent, groups entries by session and marks anything that looks destructive, network-facing or outside the project directory."
license: CC-BY-4.0
compatibility: "Needs access to: Terminal, GitHub, Slack, Notes."
metadata:
  author: "BotBento Editorial"
  version: "2026-11-05"
  source: "https://botbento.com/usecases/review-coding-agent-command-logs-for-risky/"
  kind: workflow
  hermes:
    tags: ["audit", "security", "logs", "devops"]
    category: ops
---
# Review coding agent command logs for risky entries

Flag and summarize shell commands an agent ran, ready for human review

## When to use

Each day the bot reads the command history left behind by an automated coding agent, groups entries by session and marks anything that looks destructive, network-facing or outside the project directory. It writes a short digest of what ran and what the agent appeared to be doing, lists flagged entries with their exact command text, and leaves any cleanup decision to the person reviewing.

## Steps

1. On a schedule: Daily command log review
2. Classify commands by risk
3. Digest of flagged commands

## Instructions

You audit the shell activity of an automated coding agent. Read the command log for the past day, group entries by session, and note the apparent goal of each session. Classify every command as routine, needs a second look, or risky, judging by whether it deletes or overwrites files, changes permissions, opens network connections, installs software, or reaches outside the repository. Compose a digest covering what ran, which entries were flagged, and the exact text of each flagged command. Do not delete, redact, repair or re-run anything yourself, and do not contact anyone: queue suggested fixes and any outgoing messages for the user to approve first.

## Source

Summarized in our own words from [Show HN: Stroq – a local audit of what your coding agent did and why](https://news.ycombinator.com/item?id=50380704) (Hacker News, checked 2026-11-05). Any results described there are the authors’ own.

From the BotBento use-case directory: https://botbento.com/usecases/review-coding-agent-command-logs-for-risky/. Licence: [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/).
