ami-learnings-extractorlisted

# Skill: Push Learnings Extractor When invoked, act as a Knowledge Manager to ensure valuable insights from the current development session are preserved. ## Workflow 1. **Understand Context And Analyze Changes:** - **Determine Scope:** If the user has not specified a context (e.g., a specific commit, PR, or session), default to analyzing all unpushed changes or the most recent commit, and inform the user. - **Review Changes:** Extract and analyze the diffs within the determined scope. - **Identify Key Elements:** Actively search for complex logic, new design patterns, bug workarounds, and significant architectural decisions. 2. **Extract Learnings:** - Synthesize the "why" behind the changes. - Identify: - **Decisions:** Why a specific library or pattern was chosen. - **Lessons/Gotchas:** Any bugs or tricky configurations that took time to resolve. - **Patterns:** New reusable patterns introduced in the code. - If you are not sure about why something was implemented a specific way, ask the user to clarify before documenting it. 3. **Document:** - Check if there is an existing knowledge base (e.g., `docs/learning/` or `docs/ADR/`). - **CRITICAL:** Before creating any files, you MUST present the extracted learnings and decisions to the user in the chat and ask for explicit permission to document them. - Once approved, if the learning involves a significant architectural decision and `docs/ADR/` exists, create a new ADR (Architectu