What problem does it solve? Developers adding new mutations (save, approve, delete, rename) to the FiberCell Otgruzka app often forget to write audit journal entries, or write them to the wrong journal. This Skill ensures every user action is correctly logged to the right store (auditLog, warehouse.auditLog, hrJournal, itemHistories) before anyone claims "it's logged". ## Core Features & Use Cases - Journal API Routing: Maps each action type to the correct logging API — appendAudit for timesheets/HR/finance, appendWarehouseAudit for warehouse documents, appendItemHistory for item renames, appendEmployeeJournal for employee changes. - Mutation Checklist: Provides a checklist for new mutations covering actor fields, old→new rename details, AuditEntry action registration, and ring-buffer limits (2000/300/200 entries). - Use Case: When adding a "Rename Brigade" button, use this Skill to confirm the rename writes old→new values via appendAudit with actor fields, and that the new action is registered in AuditEntry labels and classification. ## Quick Start Ask the AI to verify whether a new mutation in the Otgruzka codebase writes the correct audit journal entry using the fst-action-journals checklist.
