---

title: Session: Audit Actions Separation tags: [journal, session, audit, actions] created: 2026-05-22 updated: 2026-05-22 status: active related:

• “2026-05-22-audit-command-overhaul”

---

Session: Audit Actions Separation

Date: 2026-05-22 Scope: .opencode/commands/audit.md

Summary

Added human-in-the-loop separation to /audit: audit reports issues and proposes actions, but only writes actions.md after user review. Prevents audit from silently committing to actions the user hasn’t vetted.

Key Learnings

New Patterns

• Report-then-confirm pattern: Audit commands should report findings first, ask for review, then store approved items. Don’t write action files during the audit pass — write them after human confirmation. This keeps the audit read-only and lets the user curate what’s worth tracking.

Decisions

• Single actions.md file at knowledge/inventory/audit/actions.md — not per-component action files. One file makes it easy to see everything at once and pick items off in any session.
• Append, don’t overwrite: When actions.md already exists, append new actions and avoid duplicates. Enables incremental re-audits without losing progress on in-flight actions.
• Markdown task list format: - [ ] [P0] component: issue — action. Check off when done. Re-run /audit to regenerate.

Skill Updates Needed

• patterns skill: Add “report-then-confirm” pattern — applicable to any command that proposes actions (not just /audit).

Files Modified

• .opencode/commands/audit.md — added Step 9 (Store Actions) separating report from action storage