retro-automation-workflow

What problem does it solve?

Projects with automated tests, Editor/CLI runs, and TDD workflows often lose lessons, ad-hoc fixes, and decision rationale into ephemeral logs or agent chat; this Skill captures those outcomes, structures them as knowledge/gotchas/rules, and ensures workflow upgrades are persisted and traceable in the Kit repository.

Core Features & Use Cases

• Structured Retrospective Extraction: read recent git logs, test outputs, and Kit knowledge to identify DecisionPoints, root causes, actions taken, and verification steps.
• Create Durable Artifacts: convert findings into gotcha entries, dev procedure updates, rule/skill recommendations, and a Mermaid flowchart to document the evolved workflow.
• Enforce Traceability: stage and commit workflow changes in the Kit with atomic, UTF-8 Chinese commit subjects when requested, and report back commit hashes for audit.
• Use Case: after an unattended UE automation run fails, run this Skill to extract failure evidence, promote critical inbox items to knowledge, update gatekeeping test playbooks, and produce a visual flowchart showing the revised automation path.

Quick Start

Perform a retro on the last automation run, extract gotchas and decision points, write or update the relevant content/knowledge and content/dev files with a Mermaid flowchart, and commit the workflow changes to the Kit repository.