# Sop Session Audit

> Use this skill when writing a session audit file. Triggers: creating audit, writing to .claude/audits/, documenting session work, capturing design decisions, recording feedback from user.

- Skill: `machow/sop-session-audit` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add machow/sop-session-audit`
- Raw SKILL.md: https://api.skillmd.com/api/skills/machow/sop-session-audit/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Security
- Author: machow (https://skillmd.com/u/machow)
- Updated: 2026-09-10
- Page: https://skillmd.com/skills/machow/sop-session-audit

---


# Session Audit SOP

## Goal

Capture what matters from a session:
- **What we did** - changes made, files modified
- **Key decisions** - choices and their rationale
- **Important feedback** - user corrections that shaped the work
- **Patterns to remember** - lessons for future sessions

## Procedure

1. **Name the file with date**: `.claude/audits/YYYY-MM-DD-feature-name.md`
   ```bash
   /bin/date +%Y-%m-%d  # get current date
   ```

2. **Write audit following template**: See [TEMPLATE.md](TEMPLATE.md)

3. **Ensure feedback captures conversation flow** - not just the end result, but the progression of corrections

4. **If no feedback recorded, think carefully** - most sessions have at least some course corrections worth noting

5. **Summarize to user after writing**: Report back with:
   - Audit file name
   - Key feedback points (quote the "Important Feedback" section)
   - Patterns learned (list from "Patterns to Remember")

   This ensures the user sees what was captured without having to open the file.

**Note**: Audit files are gitignored - don't commit them.