add a verify step to ensure all patch set versions are downloaded

Author: zhjwpku

.cursor/skills/pgweekly-blog-generation/SKILL.md

@@ -22,11 +22,19 @@ Generates English and Chinese technical blog posts from PostgreSQL mailing list
    - `attachments/` - **Downloaded patches** (e.g. `.patch` files from the mailing list)
    - `attachments.txt` - List of downloaded attachment filenames
 
-3. **Analyze** content:
+3. **Verify** all patch set versions are downloaded (required before analyze):
+   - Read `thread.md` and `thread.html` to identify all patch versions referenced in the thread (e.g. v1, v2, v3, v4, v5…; also patterns like `0001-`, `0002-` in patch series)
+   - List files in `attachments/` and compare: every referenced version must have a corresponding downloaded file
+   - If any referenced version is missing:
+     - Run `python3 tools/fetch_data.py --thread-dir "data/threads/YYYY-MM-DD/<thread-id>"` to retry downloading missing attachments
+     - If still missing, do not proceed with analysis; report the missing versions and ask the user to verify the thread or manually add the patches
+   - Only proceed to analyze/generate once all referenced patch versions are present in `attachments/`
+
+4. **Analyze** content:
    - If multiple patch versions (v1, v2, v3...), run `diff -u` between versions to explain evolution
    - Identify main topic, key decisions, reviewer feedback
 
-4. **Generate** TWO blog posts with this structure:
+5. **Generate** TWO blog posts with this structure:
    - Clear title (topic-based)
    - Introduction (context, why it matters)
    - Technical Analysis (key points, code/patch highlights, evolution)
@@ -35,12 +43,12 @@ Generates English and Chinese technical blog posts from PostgreSQL mailing list
    - Current Status (patch/discussion state)
    - Conclusion (summary, implications)
 
-5. **Save** both versions:
+6. **Save** both versions:
    - English: `src/en/{year}/{week}/{descriptive-filename}.md`
    - Chinese: `src/cn/{year}/{week}/{descriptive-filename}.md`
    - Filename: kebab-case from main topic (e.g. `planner-count-optimization`)
 
-6. **Update** SUMMARY.md and year READMEs:
+7. **Update** SUMMARY.md and year READMEs:
    - Add entries under both `# 🇬🇧 English` and `# 🇨🇳 中文`
    - Follow existing hierarchy: year → week → link to article
    - **Put the new week/article at the top** (newest first): insert the new week immediately after the year line, so the latest week appears first in the list.

BLOG_GENERATION_PROMPT.md

@@ -19,13 +19,18 @@ I need you to act as a PostgreSQL expert and technical writer to generate a high
    - Run: `python3 tools/fetch_data.py --thread-id "{THREAD_ID_OR_URL}"`
    - This will download the HTML, convert to Markdown, and save attachments
 
-2. **Analyze the content:**
+2. **Verify all patch set versions are downloaded:**
+   - Identify all patch versions referenced in the thread (v1, v2, v3…; or 0001-, 0002- in patch series)
+   - Ensure every referenced version exists in `attachments/`
+   - If any are missing, run `python3 tools/fetch_data.py --thread-dir "data/threads/YYYY-MM-DD/<thread-id>"` to retry; do not proceed until all are present
+
+3. **Analyze the content:**
    - Read the converted Markdown file in `data/threads/YYYY-MM-DD/<thread-id>/thread.md`
    - Review the original HTML if you need more context
    - Check the `attachments/` folder for any patch files
    - If there are multiple patch versions (v1, v2, v3, etc.), use `diff` to understand what changed between versions
 
-3. **Generate a technical blog post with:**
+4. **Generate a technical blog post with:**
    - **Clear title:** Based on the main topic discussed
    - **Introduction:** Brief context and why this matters
    - **Technical Analysis:**
@@ -42,12 +47,12 @@ I need you to act as a PostgreSQL expert and technical writer to generate a high
    - **Current Status:** Where the patch/discussion stands
    - **Conclusion:** Summary and implications for PostgreSQL users
 
-4. **Write TWO versions (English and Chinese):**
+5. **Write TWO versions (English and Chinese):**
    - **English version:** Professional technical writing style, clear explanations
    - **Chinese version:** Professional Chinese technical writing, natural terminology
    - **Both versions:** Code blocks with proper syntax highlighting, links to documentation
 
-5. **Save the blogs:**
+6. **Save the blogs:**
    - Determine the appropriate year and week number based on the thread date or current date
    - Generate a descriptive filename based on the content
    - **Create directories if needed and save TWO files:**
@@ -80,13 +85,17 @@ Act as a PostgreSQL core developer and technical writer. Generate a comprehensiv
 **Step 1: Data Collection**
 Run: `python3 tools/fetch_data.py --thread-id "{THREAD_ID_OR_URL}"`
 
-**Step 2: Content Analysis**
+**Step 2: Verify Patch Versions**
+- Identify all patch versions referenced in the thread (v1, v2, v3…; 0001-, 0002-…)
+- Ensure every referenced version exists in `attachments/`; if any missing, run `python3 tools/fetch_data.py --thread-dir "data/threads/YYYY-MM-DD/<thread-id>"` and do not proceed until all are present
+
+**Step 3: Content Analysis**
 Review:
 - Markdown content: `data/threads/*/thread.md`
 - Patches in: `data/threads/*/attachments/`
 - For multiple patch versions, run: `diff -u v1-*.patch v2-*.patch` to see evolution
 
-**Step 3: Blog Structure**
+**Step 4: Blog Structure**
 
 Create a blog with these sections:
 
@@ -153,7 +162,7 @@ For each major version:
 - Related documentation
 - Previous related discussions (if mentioned)
 
-**Step 4: File Management**
+**Step 5: File Management**
 - Determine year and week: [Calculate from thread date or today's date]
 - Create paths: `src/en/{year}/{week}/` and `src/cn/{year}/{week}/`
 - Filename: [Generate from main topic, lowercase-with-hyphens]
@@ -191,16 +200,17 @@ For faster processing:
 Generate a PostgreSQL technical blog from this thread: {THREAD_ID_OR_URL}
 
 1. Fetch: `python3 tools/fetch_data.py --thread-id "{THREAD_ID_OR_URL}"`
-2. Read the Markdown content and patches
-3. Compare patch versions if multiple exist (use diff)
-4. Write a technical blog covering:
+2. Verify all patch set versions referenced in the thread are downloaded; retry with `--thread-dir` if any are missing; do not proceed until all are present
+3. Read the Markdown content and patches
+4. Compare patch versions if multiple exist (use diff)
+5. Write a technical blog covering:
    - What problem is being solved
    - How the solution works
    - Key discussion points
    - Patch evolution (if applicable)
    - Current status
-5. Save to: `src/{year}/{appropriate-week}/{descriptive-name}.md`
-6. Update `src/SUMMARY.md`
+6. Save to: `src/{year}/{appropriate-week}/{descriptive-name}.md`
+7. Update `src/SUMMARY.md`
 
 Write as a PostgreSQL expert. Focus on technical accuracy and clarity.
 ```
@@ -250,11 +260,12 @@ I have {N} PostgreSQL mailing list threads to convert into blog posts. Process t
 
 For each thread:
 1. Fetch data: `python3 tools/fetch_data.py --thread-id "{THREAD_ID}"`
-2. Generate TWO versions of the technical blog post (English and Chinese)
-3. Save to appropriate year/week directories:
+2. Verify all patch set versions referenced in the thread are downloaded; retry with `--thread-dir` if needed; do not proceed until all are present
+3. Generate TWO versions of the technical blog post (English and Chinese)
+4. Save to appropriate year/week directories:
    - English: `src/en/{year}/{week}/{filename}.md`
    - Chinese: `src/cn/{year}/{week}/{filename}.md`
-4. Update `src/SUMMARY.md` in both language sections
+5. Update `src/SUMMARY.md` in both language sections
 
 After all are done, provide a summary of:
 - Blogs created