Audit What Happened During a Session - AI Skills
How-to Guide
Author:
Fluent Commerce
Changed on:
31 Mar 2026
Key Points
[Warning: empty required content area]Prerequisites
Steps
Generate Quick Summary
`What did we change this session?``/fluent-session` shows three tables:Skill Invocations: | Skill | Gate | Outcome | Next |- fluent-rule-scaffold
- PASS
- completed
- fluent-build
- fluent-build
- PASS
- completed
- fluent-pre-deploy-check
- fluent-pre-deploy-check
- READY
- completed
- fluent-module-deploy
- fluent-module-deploy
- PASS
- completed
- fluent-e2e-test
- entity_create
- ORDER/E2E_HD_001
- Yes
- ok
- fluent-e2e-test
- event_send
- ORDER/E2E_HD_001
- Yes
- ok
- fluent-e2e-test
- test_assert
- ORDER/E2E_HD_001 status=BOOKED
- No
- ok
- fluent-e2e-test
- CREATE
- src/.../ValidateReturnWindow.java
- New rule class
- MODIFY
- resources/module.json
- Registered ValidateReturnWindow
- DEPLOY
- fc-module-my-returns 1.4.0
- Installed to MY_RETAILER
Machine-Readable Export
`Export a JSON audit trail``/fluent-session export` writes a JSON file to `accounts/<PROFILE>/sessions/` with: - `skillInvocations[]` — full decision chain with gate results, handoff signals, cross-references - `toolCalls[]` — every MCP tool call with target, outcome, triggering skill - `changes[]` — every state mutation with rollback commands - `decisionTrail[]` — explicit branch decisions with rationale and confidence - `compliance` — scope traceability matrix, task completion statusThe JSON is designed for CI/CD consumption — parse it as a deployment gate, feed it into Jira work logs, or attach to Confluence release pages.
