refactor: Simplify Claude review and translation sync workflow instructions

Author: josix

.github/workflows/claude-review.yml

@@ -36,18 +36,11 @@ jobs:
             Bash(msgfmt:*)
           direct_prompt: |
             Review the changed PO files in this pull request for translation quality.
-
-            Use `gh pr diff ${{ github.event.pull_request.number }}` to see what changed,
-            then read the affected PO files and check for:
-
-            1. **Terminology consistency**: Cross-check against doc-translate/references/terminology.md
-            2. **zh-CN terms**: Flag simplified Chinese terms (創建→建立, 代碼→程式碼, 信息→資訊, 模塊→模組, 默認→預設, 調用→呼叫, 返回→回傳, 函數→函式, 變量→變數, 實現→實作, 數據→資料, 線程→執行緒, 內存→記憶體, 異步→非同步, 訪問→存取, 當前→目前, 文檔→文件)
-            3. **Punctuation**: Chinese sentences should use fullwidth punctuation (。，「」（）), English/code stays halfwidth
-            4. **Spacing**: Space between Chinese and English text (e.g., `使用 CPU`), no space between symbols and English
-            5. **reST syntax**: Ensure :func:, :mod:, :class:, :meth:, :ref:, :term: roles are preserved correctly
-            6. **Line length**: PO file lines should be <= 79 characters
-
-            Validate with `msgfmt --check` on changed files.
-
-            Post a concise review summarizing any issues found, grouped by category.
-            If no issues found, post a short approval comment.
+            Follow the review-translation and check-terminology skills for review criteria.
+
+            Steps:
+            1. Run `gh pr diff ${{ github.event.pull_request.number }}` to identify changed PO files
+            2. Read each changed file and review translated entries per the skill checklists
+            3. Run `msgfmt --check` on each changed file to validate
+            4. Post a concise review comment grouping issues by category
+            5. If no issues found, post a short approval comment

.github/workflows/claude-translate-sync.yml

@@ -90,76 +90,25 @@ jobs:
             You are working on the CPython sync PR #${{ steps.find-pr.outputs.pr_number }}
             on the `cron/sync/3.14` branch.
 
-            Your task is to translate new fuzzy and untranslated entries in PO files.
-
-            ## Step 1: Find entries that need work
-
-            Use `msgattrib` to find files with fuzzy or untranslated entries:
-            ```
-            msgattrib --fuzzy --only-fuzzy <file> to find fuzzy entries
-            msgattrib --untranslated --only-untranslated <file> to find untranslated entries
-            ```
-
-            Focus on files changed in this PR first:
-            ```
-            git diff --name-only origin/3.14...HEAD -- '*.po'
-            ```
-
-            ## Step 2: Prioritize fuzzy entries
-
-            Fuzzy entries already have a base translation that needs updating.
-            Compare the old msgid (`#|`) with the new msgid and update the translation.
-            Remove the `#, fuzzy` flag and `#|` comments after fixing.
-
-            ## Step 3: Translate untranslated entries
-
-            For entries with empty msgstr, provide new translations.
-
-            ## Translation rules
-
-            Follow these rules strictly:
-            - Use Traditional Chinese (zh-TW), NEVER simplified Chinese (zh-CN)
-            - Fullwidth punctuation for Chinese: 。，「」（）
-            - Add space between Chinese and English text
-            - Preserve all reST markup (:func:, :mod:, :class:, :ref:, :term: etc.)
-            - Keep these terms in English: int, float, str, bytes, list, tuple, dict, set, iterator, generator, iterable, pickle
-            - Use correct zh-TW terms: 建立(not 創建), 程式碼(not 代碼), 資訊(not 信息), 模組(not 模塊), 預設(not 默認), 呼叫(not 調用), 回傳(not 返回), 函式(not 函數), 變數(not 變量), 實作(not 實現), 資料(not 數據)
-            - Line length <= 79 characters in PO files
-
-            ## Step 4: Wrap and validate
-
-            After editing, run powrap on changed files:
-            ```
-            uvx powrap <file>
-            ```
-
-            Validate with:
-            ```
-            msgfmt --check <file>
-            ```
-
-            ## Step 5: Commit and push
-
-            Stage changed PO files and commit:
-            ```
-            git add <changed .po files>
-            git commit -m "Translate fuzzy and untranslated entries from sync"
-            git push
-            ```
-
-            ## Step 6: Post summary
-
-            Post a comment on PR #${{ steps.find-pr.outputs.pr_number }} summarizing:
-            - Number of fuzzy entries fixed
-            - Number of new translations added
-            - Files modified
-            - Any entries skipped (and why)
-
-            Use:
-            ```
-            gh pr comment ${{ steps.find-pr.outputs.pr_number }} --body "<summary>"
-            ```
-
-            If there are no fuzzy or untranslated entries to process, post a short
-            comment saying the sync PR has no entries needing translation and skip
-            the commit/push steps.
+            Your task: translate fuzzy and untranslated entries in changed PO files.
+            Follow the translate-po and fix-fuzzy skills for translation rules and fuzzy resolution.
+
+            Steps:
+            1. Find changed PO files: `git diff --name-only origin/3.14...HEAD -- '*.po'`
+            2. For each file, use `msgattrib --only-fuzzy` and `msgattrib --only-untranslated` to find entries
+            3. Prioritize fuzzy entries first (use fix-fuzzy skill), then untranslated (use translate-po skill)
+            4. After editing, run `uvx powrap <file>` and `msgfmt --check <file>`
+            5. Commit and push:
+               ```
+               git add <changed .po files>
+               git commit -m "Translate fuzzy and untranslated entries from sync"
+               git push
+               ```
+            6. Post a summary comment on PR #${{ steps.find-pr.outputs.pr_number }} with:
+               - Fuzzy entries fixed count
+               - New translations added count
+               - Files modified
+               - Entries skipped (if any, with reasons)
+               Use: `gh pr comment ${{ steps.find-pr.outputs.pr_number }} --body "<summary>"`
+
+            If no entries need work, post a short "nothing to translate" comment and skip commit/push.