---
name: action-log-narrator
description: Structures action log presentation by domain and offers revert when a snapshot exists.
version: 1.1.0
author: LolaCore Team
always: false
triggers:
  keywords: [what did you do, log, history of changes, undo, revert, qué hiciste, historial, deshacer, revertir, action log, último cambio]
priority: 60
enabled: true
writes_data: false
---

# ACTION LOG PRESENTATION

Active when the user asks what was done, wants to review change history, or asks to undo or revert an action.

## Data source

1. **MCP / REST:** Call `lolacore/get-action-history`. Optional filters: `action_type`, `status`, `limit` (1–100, default 20). There is no time-range parameter — fetch recent rows and filter in your summary when the user asks for a window (e.g., "last 24 hours").
2. **Web chat:** There is no dedicated action-history tool in the chat toolset. Summarize actions from confirmed cards in the current session when they are recent. For older history, use MCP if available, or explain that executed actions are stored in `wp_lolacore_log` and surfaced through the action-history ability outside the web chat tool surface.

## Presentation format

1. Group results by domain: content, plugins, woocommerce, users, database, plugin builder. Never list linearly.
2. For each action: `timestamp | ability | outcome | reversible: yes/no`.
3. Highlight irreversible actions explicitly — the user must notice them.

## Revert flow

- **Built plugins:** Each Plugin Builder update saves a post revision. The user can roll back from the Built Plugins library entry.
- **Other actions:** Log rows may store before/after data in `details`, but there is no automatic revert tool in chat. If a snapshot or enough detail exists, describe what would need to be restored and ask for explicit confirmation before re-running the inverse action manually.
- **No snapshot or detail:** Be direct: "This action is not automatically reversible. You would need to recreate the change manually."

## Scope

This skill covers changes to persistent WordPress data logged by LolaCore. "Undo the CSS rule" or "remove that filter from functions.php" is out of scope — those are not logged actions.
