Merge branch 'DIYgod:master' into master

Author: chuck-shi

.github/prompts/pr_review_rules.md

@@ -0,0 +1,50 @@
+# PR Review Rules for RSSHub
+
+You are reviewing pull requests for RSSHub.
+
+Only report **clear and actionable** violations in changed lines/files. Do not report speculative or uncertain issues.
+
+## Route Metadata and Docs
+
+1. `example` must start with `/` and be a working RSSHub route path.
+2. Route name must not repeat namespace name.
+3. In radar rules, `source` must be a relative host/path (no `https://`, no hash/query matching).
+4. In radar rules, `target` must match the route path and declared params.
+5. Namespace `url` should not include protocol prefix.
+6. Use a single category in `categories`.
+7. `parameters` keys must match real path parameters.
+8. Keep route/docs lists in alphabetical order when touching sorted files.
+9. Do not modify default values or working examples unless they are broken.
+
+## Data Handling and Feed Quality
+
+10. Use `cache.tryGet()` (from `@/utils/cache`) for detail fetching in loops; cache processed result instead of raw HTML.
+11. `description` should contain article content only; do not duplicate `title`, `author`, `pubDate`, or tags.
+12. Extract tags/categories into `category` field.
+13. Use `parseDate()` for date fields when source provides time.
+14. Do not set fake dates (`new Date()` fallback) when source has no valid time.
+15. Keep each item `link` unique; feed-level `link` should be human-readable (not raw API endpoint).
+16. Do not trim/truncate title/content manually.
+
+## API and Requesting
+
+17. Prefer official API endpoints over scraping when available.
+18. Fetch first page only; do not add custom pagination behavior.
+19. Use common parameter `limit` instead of custom limit/query filtering.
+20. Prefer path parameters over custom query parameters for route config.
+21. Use RSSHub built-in UA behavior; when browser-like headers are needed, use `config.trueUA` instead of hardcoded UA strings.
+
+## Code Style and Maintainability
+
+22. Use `camelCase` naming.
+23. Use `import type { ... }` for type-only imports.
+24. Keep imports sorted.
+25. Use JSX-based rendering (`renderToString` and template components) for custom HTML rendering patterns used by RSSHub.
+26. Avoid unnecessary changes outside PR scope.
+
+## Reporting Format
+
+- Report only violated rules.
+- Each bullet should include: file path, problem, and concrete fix.
+- Group repeated issues across files into one concise bullet when possible.
+- If no rule is clearly violated, do not comment.

.github/prompts/similar_issues.prompt.yml

@@ -107,7 +107,7 @@ jobs:
 
             - name: Build and push Docker image (ordinary version)
               id: build-and-push
-              uses: docker/build-push-action@263435318d21b8e681c14492fe198d362a7d2c83 # v6.18.0
+              uses: docker/build-push-action@601a80b39c9405e50806ae38af30926f9d957c47 # v6.19.1
               with:
                   context: .
                   tags: ${{ steps.image-name-ordinary.outputs.tags }}
@@ -160,7 +160,7 @@ jobs:
 
             - name: Build and push Docker image (Chromium-bundled version)
               id: build-and-push-chromium
-              uses: docker/build-push-action@263435318d21b8e681c14492fe198d362a7d2c83 # v6.18.0
+              uses: docker/build-push-action@601a80b39c9405e50806ae38af30926f9d957c47 # v6.19.1
               with:
                   context: .
                   build-args: PUPPETEER_SKIP_DOWNLOAD=0

.github/workflows/docker-release.yml

@@ -121,7 +121,7 @@ jobs:
 
             - name: Pull Request Labeler
               if: ${{ failure() }}
-              uses: actions-cool/issues-helper@e2ff99831a4f13625d35064e2b3dfe65c07a0396 # v3.7.5
+              uses: actions-cool/issues-helper@71b62d7da76e59ff7b193904feb6e77d4dbb2777 # v3.7.6
               with:
                   actions: 'add-labels'
                   token: ${{ secrets.GITHUB_TOKEN }}
@@ -161,7 +161,7 @@ jobs:
                     >> "${GITHUB_OUTPUT}"
 
             - name: Pull Request Labeler
-              uses: actions-cool/issues-helper@e2ff99831a4f13625d35064e2b3dfe65c07a0396 # v3.7.5
+              uses: actions-cool/issues-helper@71b62d7da76e59ff7b193904feb6e77d4dbb2777 # v3.7.6
               with:
                   actions: 'add-labels'
                   token: ${{ secrets.GITHUB_TOKEN }}

.github/workflows/docker-test-cont.yml

@@ -40,7 +40,7 @@ jobs:
                   flavor: latest=true
 
             - name: Build Docker image
-              uses: docker/build-push-action@263435318d21b8e681c14492fe198d362a7d2c83 # v6.18.0
+              uses: docker/build-push-action@601a80b39c9405e50806ae38af30926f9d957c47 # v6.19.1
               with:
                   context: .
                   build-args: PUPPETEER_SKIP_DOWNLOAD=0 # also test bundling Chromium
@@ -55,7 +55,7 @@ jobs:
 
             - name: Pull Request Labeler
               if: ${{ failure() }}
-              uses: actions-cool/issues-helper@e2ff99831a4f13625d35064e2b3dfe65c07a0396 # v3.7.5
+              uses: actions-cool/issues-helper@71b62d7da76e59ff7b193904feb6e77d4dbb2777 # v3.7.6
               with:
                   actions: 'add-labels'
                   token: ${{ secrets.GITHUB_TOKEN }}

.github/workflows/docker-test.yml

@@ -0,0 +1,96 @@
+name: pr-review
+
+on:
+    pull_request_target:
+        types: [opened, reopened, synchronize, ready_for_review]
+    workflow_dispatch:
+        inputs:
+            pr_number:
+                description: Pull request number to review manually
+                required: true
+                type: number
+
+jobs:
+    review-pr:
+        if: github.event_name == 'workflow_dispatch' || github.event.pull_request.draft == false
+        runs-on: ubuntu-latest
+        timeout-minutes: 10
+        permissions:
+            contents: read
+            issues: write
+            pull-requests: write
+        steps:
+            - name: Checkout repository
+              uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+
+            - name: Set up Bun
+              uses: oven-sh/setup-bun@3d267786b128fe76c2f16a390aa2448b815359f3 # v2.1.2
+
+            - name: Install opencode
+              run: curl -fsSL https://opencode.ai/install | bash
+
+            - name: Review PR with rules
+              env:
+                  OPENCODE_API_KEY: ${{ secrets.OPENCODE_API_KEY }}
+                  GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+                  GITHUB_REPOSITORY: ${{ github.repository }}
+                  PR_NUMBER: ${{ github.event.pull_request.number || inputs.pr_number }}
+                  OPENCODE_PERMISSION: |
+                      {
+                        "bash": {
+                          "*": "deny",
+                          "gh auth*": "allow",
+                          "gh pr*": "allow",
+                          "gh api*": "allow"
+                        },
+                        "webfetch": "deny"
+                      }
+              run: |
+                  if [ -z "$PR_NUMBER" ]; then
+                    echo "pr_number is required"
+                    exit 1
+                  fi
+
+                  RULES=$(cat .github/prompts/pr_review_rules.md)
+
+                  opencode run -m ${{ vars.OPENCODE_MODEL }} "A pull request has been created or updated in this repository.
+
+                  Pull request number:
+                  $PR_NUMBER
+
+                  Repository:
+                  $GITHUB_REPOSITORY
+
+                  Your task:
+                  1. Use GitHub CLI commands to inspect this PR's metadata and code changes.
+                  2. Review only based on the following rules.
+                  3. Report only clear and actionable violations from changed files.
+                  4. If no clear violations are found, do not comment.
+
+                  Review rules:
+                  $RULES
+
+                  Required behavior:
+                  - Keep feedback concise and grouped by rule.
+                  - Include file path and a concrete fix suggestion for each issue.
+                  - Ignore uncertain or low-confidence findings.
+                  - Avoid duplicate comments.
+
+                  Comment protocol:
+                  - Use marker: <!-- pr-auto-review -->
+                  - Check existing comments in issue comments for this marker.
+                  - If a marker comment exists, update it with latest findings.
+                  - Otherwise create a new PR comment.
+                  - If there are no findings and marker comment exists, edit marker comment to a short pass status.
+
+                  Suggested comment format:
+                  <!-- pr-auto-review -->
+                  ## Auto Review
+                  - [Rule] file: issue + suggestion
+
+                  For no findings:
+                  <!-- pr-auto-review -->
+                  ## Auto Review
+                  No clear rule violations found in the current diff.
+
+                  Use only gh commands and repository data."

.github/workflows/pr-review.yml

@@ -1,91 +1,71 @@
-name: Similar Issues via AI MCP
+name: duplicate-issues
 
 on:
     issues:
         types: [opened]
+    workflow_dispatch:
+        inputs:
+            issue_number:
+                description: Issue number to check manually
+                required: true
+                type: number
 
 jobs:
-    find-similar:
+    check-duplicates:
+        runs-on: ubuntu-latest
         permissions:
             contents: read
             issues: write
-            models: read
-        runs-on: ubuntu-slim
         steps:
-            - name: Check out repository
+            - name: Checkout repository
               uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
 
-            - name: Prepare prompt variables
-              id: prepare_input
-              uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8.0.0
-              with:
-                  script: |
-                      const issue = context.payload.issue || {};
-                      const title = issue.title || '';
-                      const body = issue.body || '';
-                      const indent = '      ';
-                      // Indent subsequent lines so YAML block scalar indentation remains valid
-                      const bodyIndented = body.replace(/\n/g, '\n' + indent);
-                      core.setOutput('issue_title_json', JSON.stringify(title));
-                      core.setOutput('issue_body_indented_json', JSON.stringify(bodyIndented));
-                      core.setOutput('issue_number', issue.number);
+            - name: Set up Bun
+              uses: oven-sh/setup-bun@3d267786b128fe76c2f16a390aa2448b815359f3 # v2.1.2
 
-            - name: Find similar issues with AI (MCP)
-              id: inference
-              uses: actions/ai-inference@a380166897b5408b8fb7dddd148142794cb5624a # v2.0.6
-              with:
-                  prompt-file: ./.github/prompts/similar_issues.prompt.yml
-                  input: |
-                      issue_title: ${{ steps.prepare_input.outputs.issue_title_json }}
-                      issue_body: ${{ steps.prepare_input.outputs.issue_body_indented_json }}
-                      issue_number: ${{ steps.prepare_input.outputs.issue_number }}
-                      repository: ${{ github.repository }}
-                  enable-github-mcp: true
-                  # Inference token can use GITHUB_TOKEN. MCP specifically requires a PAT.
-                  token: ${{ secrets.GITHUB_TOKEN }}
-                  github-mcp-token: ${{ secrets.USER_PAT }}
-                  max-tokens: 8000
+            - name: Install opencode
+              run: curl -fsSL https://opencode.ai/install | bash
 
-            - name: Prepare comment body
-              id: prepare
-              uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8.0.0
+            - name: Check for duplicate issues
               env:
-                  AI_RESPONSE: ${{ steps.inference.outputs.response }}
-              with:
-                  script: |
-                      let data;
-                      try {
-                        data = JSON.parse(process.env.AI_RESPONSE || '{}');
-                      } catch (e) {
-                        core.setOutput('has_matches', 'false');
-                        return;
+                  OPENCODE_API_KEY: ${{ secrets.OPENCODE_API_KEY }}
+                  GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+                  ISSUE_NUMBER: ${{ github.event.issue.number || inputs.issue_number }}
+                  OPENCODE_PERMISSION: |
+                      {
+                        "bash": {
+                          "*": "deny",
+                          "gh issue*": "allow"
+                        },
+                        "webfetch": "deny"
                       }
-                      const matches = Array.isArray(data.matches) ? data.matches.filter(m => m.number !== context.payload.issue.number) : [];
-                      if (!matches.length) {
-                        core.setOutput('has_matches', 'false');
-                        return;
-                      }
-                      const lines = [];
-                      lines.push('I found similar issues that might help:');
-                      for (const m of matches.slice(0, 3)) {
-                        const num = m.number != null ? `#${m.number}` : '';
-                        const title = m.title || 'Untitled';
-                        const url = m.url || '';
-                        const score = typeof m.similarity_score === 'number' ? ` (similarity: ${m.similarity_score.toFixed(2)})` : '';
-                        lines.push(`- ${url}${score}`.trim());
-                      }
-                      core.setOutput('has_matches', 'true');
-                      core.setOutput('comment_body', lines.join('\n'));
+              run: |
+                  if [ -z "$ISSUE_NUMBER" ]; then
+                    echo "issue_number is required"
+                    exit 1
+                  fi
+
+                  opencode run -m ${{ vars.OPENCODE_MODEL }} "A new issue has been created:'
+
+                  Issue number:
+                  $ISSUE_NUMBER
+
+                  Lookup this issue and search through existing issues (excluding #$ISSUE_NUMBER) in this repository to find any potential duplicates of this new issue.
+                  Consider:
+                  1. Similar titles or descriptions
+                  2. Same error messages or symptoms
+                  3. Related functionality or components
+                  4. Similar feature requests
+
+                  If you find any potential duplicates, please comment on the new issue with:
+                  - A brief explanation of why it might be a duplicate
+                  - Links to the potentially duplicate issues
+                  - A suggestion to check those issues first
+
+                  Use this format for the comment:
+                  'This issue might be a duplicate of existing issues. Please check:
+                  - #[issue_number]: [brief description of similarity]
+
+                  Feel free to ignore if none of these address your specific case.'
 
-            - name: Comment similar issues
-              if: steps.prepare.outputs.has_matches == 'true'
-              uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8.0.0
-              with:
-                  script: |
-                      const body = ${{ toJson(steps.prepare.outputs.comment_body) }};
-                      await github.rest.issues.createComment({
-                        owner: context.repo.owner,
-                        repo: context.repo.repo,
-                        issue_number: context.payload.issue.number,
-                        body
-                      });
+                  If no clear duplicates are found, do not comment."