Add /remember-learnings skill to capture session insights (#2467)

.claude/commands/dyad/pr-push.md

@@ -65,9 +65,21 @@ Commit any uncommitted changes, run lint checks, fix any issues, and push the cu
    git commit --amend --no-edit
    ```
 
-   **IMPORTANT:** Do NOT stop here. You MUST continue to step 6 to push.
+   **IMPORTANT:** Do NOT stop here. You MUST continue to step 6.
 
-6. **Push the branch (REQUIRED):**
+6. **Remember learnings:**
+
+   Run the `/remember-learnings` skill to capture any errors, snags, or insights from this session into `AGENTS.md`.
+
+   If `AGENTS.md` was modified by the skill, amend the latest commit to include the changes:
+
+   ```
+   git diff --cached --quiet AGENTS.md || git commit --amend --no-edit
+   ```
+
+   This conditional guard ensures the commit is only amended if `AGENTS.md` actually changed, avoiding unnecessary history rewrites.
+
+7. **Push the branch (REQUIRED):**
 
    You MUST push the branch to GitHub. Do NOT skip this step or ask for confirmation.
 
@@ -83,7 +95,7 @@ Commit any uncommitted changes, run lint checks, fix any issues, and push the cu
 
    Note: `--force-with-lease` is used because the commit may have been amended. It's safer than `--force` as it will fail if someone else has pushed to the branch.
 
-7. **Create or update the PR (REQUIRED):**
+8. **Create or update the PR (REQUIRED):**
 
    **CRITICAL:** Do NOT tell the user to visit a URL to create a PR. You MUST create it automatically.
 
@@ -123,11 +135,12 @@ Commit any uncommitted changes, run lint checks, fix any issues, and push the cu
    gh pr edit --add-label "cc:request"
    ```
 
-8. **Summarize the results:**
+9. **Summarize the results:**
    - Report if a new feature branch was created (and its name)
    - Report any uncommitted changes that were committed in step 2
    - Report any files that were IGNORED and not committed (if any), explaining why they were skipped
    - Report any lint fixes that were applied
    - Confirm tests passed
    - Confirm the branch has been pushed
+   - Report any learnings added to `AGENTS.md`
    - **Include the PR URL** (either newly created or existing)

.claude/commands/remember-learnings.md

+# Remember Learnings
+
+Review the current session for errors, issues, snags, and hard-won knowledge, then update `AGENTS.md` with actionable learnings so future agent sessions run more smoothly.
+
+**IMPORTANT:** This skill MUST complete autonomously. Do NOT ask for user confirmation.
+
+## File relationship
+
+> **NOTE:** `CLAUDE.md` is a symlink to `AGENTS.md`. They are the same file. **ALL EDITS MUST BE MADE TO `AGENTS.md`**, never to `CLAUDE.md` directly.
+
+- **`AGENTS.md`** contains agent-specific operational knowledge — tips, gotchas, and hard-won insights that help agents avoid repeating mistakes.
+
+Learnings should go into `AGENTS.md`. If a learning is important enough to be a project-wide convention, flag it in the summary so a human can promote it to the project documentation.
+
+## Instructions
+
+1. **Analyze the session for learnings:**
+
+   Review the entire conversation history and identify:
+   - **Errors encountered:** Build failures, lint errors, type errors, test failures, runtime errors
+   - **Snags and gotchas:** Things that took multiple attempts, unexpected behavior, tricky configurations
+   - **Workflow friction:** Steps that were done in the wrong order, missing prerequisites, commands that needed special flags
+   - **Architecture insights:** Patterns that weren't obvious, file locations that were hard to find, implicit conventions not documented
+
+   Skip anything that is already well-documented in `AGENTS.md`.
+
+2. **Read existing documentation:**
+
+   Read `AGENTS.md` at the repository root to understand what's already documented and avoid duplication.
+
+3. **Draft concise, actionable additions:**
+
+   For each learning, write a short bullet point or section that would help a future agent avoid the same issue. Follow these rules:
+   - Be specific and actionable (e.g., "Run `npm run build` before E2E tests" not "remember to build first")
+   - Include the actual error message or symptom when relevant so agents can recognize the situation
+   - Don't duplicate what's already in `AGENTS.md`
+   - Group related learnings under existing sections if appropriate, or create a new section
+   - Keep it concise: each learning should be 1-3 lines max
+   - **Limit to at most 5 learnings per session** — focus on the most impactful insights
+   - If a new learning overlaps with or supersedes an existing one, consolidate them into a single entry rather than appending
+
+4. **Update AGENTS.md:**
+
+   Edit `AGENTS.md` to incorporate the new learnings. Add a `## Learnings` section at the bottom if one doesn't exist, or append to the existing `## Learnings` section.
+
+   If there are no new learnings worth recording (i.e., everything went smoothly or all issues are already documented), skip the edit and report that no updates were needed.
+
+   **Maintenance:** When adding new learnings, review the existing `## Learnings` section and remove any entries that are:
+   - Obsolete due to codebase changes
+   - Duplicated by or subsumed by a newer, more complete learning
+
+5. **Stage the changes:**
+
+   If `AGENTS.md` was modified:
+
+   ```
+   git add AGENTS.md
+   ```
+
+6. **Summarize:**
+   - List the learnings that were added (or state that none were needed)
+   - Confirm whether `AGENTS.md` was staged for commit