Who it is forA tech lead who wants an independent review of a module before deciding what to change.
The problemReviews done by a write-enabled agent can change files by accident, and reading agent output without a clear record of what was checked is hard to trust.
The outcomeRead-only audit tasks that produce findings and a summary for each task, with no changes to the repository.
What you need first
- Node.js 20 or newer
- git, for task isolation
- At least one of Claude Code, Codex or OpenCode installed
- Optional: an API key from one of the supported providers, if you do not want a coding agent to act as the planner
Steps
- Install the CLI with
npm install -g ordewell, then open the terminal UI withordewellin your project. - Describe an audit goal, such as a security review of one module, and answer the planner's questions.
- Check in the plan that the audit tasks are set to read-only mode before you approve the run.
- Run the plan with
ordewell runand follow each task's log. - Read each task's summary and numbered findings, then decide what to fix in a separate plan.
Prompt for your agent
In the repository at <project path>, plan a read-only audit of <module or area> with Ordewell and run it. Output each audit task's summary and numbered findings with evidence. Verify that the audit tasks ran in read-only mode and that `git status` shows no changes to the repository.
Caveat. A read-only audit is only as reliable as the agent doing it, so check the cited evidence in each finding against the code before acting on it.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for ordewell/ordewell and "Run a read-only audit before any code changes"
Add Deduped to Claude Code once
claude mcp add --transport http deduped https://dedupedai.com/mcp
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer