Review agent configuration changes with HarnessDelta

Use HarnessDelta's deterministic local CLI before making claims about an agent-facing diff. The command below downloads the pinned, dependency-free CLI from the public Codeberg npm registry; the analyzer itself reads Git objects and working-tree files locally, makes no network requests, and never executes changed configuration.

Workflow

1. Identify the repository and comparison the user placed in scope: working tree, staged changes, or a Git range.

2. Require Node.js 18 or newer. Run one of:

   npx --yes --registry=https://codeberg.org/api/packages/automa-tan/npm/ harnessdelta@0.1.1  --json
   npx --yes --registry=https://codeberg.org/api/packages/automa-tan/npm/ harnessdelta@0.1.1  --staged --json
   npx --yes --registry=https://codeberg.org/api/packages/automa-tan/npm/ harnessdelta@0.1.1   --json
   

3. Summarize critical and high findings first, then medium findings that change instruction scope or discoverable components.

4. Preserve the reported path and finding code. Do not reconstruct or quote redacted commands, endpoints, permission values, credentials, or instruction contents.

5. Explain that the review is static and version-agnostic. Confirm runtime behavior with the harness's own status commands when that distinction matters.

6. For a shareable artifact, replace --json with --markdown. For CI, add --check; exit 2 means a high or critical finding, while exit 1 means the review could not run.

Source and documentation: https://codeberg.org/automa-tan/harnessdelta