ami-extract-learningslisted

# 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 & Apply Longevity Gating:** - Synthesize the "why" behind the changes. - **Quality & Enduring Value Gate:** Filter out transient trial-and-error logs, routine syntax adjustments, or low-signal one-liners. Only preserve learnings that provide enduring future value to developers or AI assistants. - Identify: - **Decisions:** Why a specific library or pattern was chosen. - **Lessons/Gotchas:** Non-trivial bugs, subtle platform edge cases, or tricky configurations that took time to resolve. - **Patterns:** New reusable architectural 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 & Deduplicate:** - Check existing repository memory (`docs/learning/`, `docs/external-references