Add Tabnine code review workflow

Author: Pavel-tabnine

.github/workflows/tabnine_cr.yml

@@ -0,0 +1,61 @@
+name: Tabnine Code Review
+on:
+  pull_request
+
+jobs:
+  code-review:
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+      pull-requests: write
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+          ref: ${{ github.event.pull_request.head.sha }}
+          
+      - name: Install Tabnine CLI
+        run: |
+          export TABNINE_HOST=https://console.tabnine.com
+          curl $TABNINE_HOST/update/cli/installer.mjs | node - $TABNINE_HOST
+          
+      - name: Configure git
+        run: |
+          git config user.name "Tabnine CLI Agent"
+          git config user.email "TabnineCLI@tabnine.com"
+
+      - name: Configure tabnine auth
+        run: |
+          mkdir -p ~/.tabnine/agent
+          echo ${{ secrets.TABNINE_KEY }} > ~/.tabnine/agent/tabnine_creds.json
+          
+      - name: Code Review
+        env:
+          GH_TOKEN: ${{ github.token }}
+          BRANCH_PREFIX: docs
+        run: |
+          tabnine -y -p "You are operating in a GitHub Actions runner performing automated code review. The gh CLI is available and authenticated via GH_TOKEN. You may comment on pull requests.
+          Context:
+          - Repo: ${{ github.repository }}
+          - PR Number: ${{ github.event.pull_request.number }}
+          - PR Head SHA: ${{ github.event.pull_request.head.sha }}
+          - PR Base SHA: ${{ github.event.pull_request.base.sha }}
+          Objectives:
+          1) Re-check existing review comments and reply resolved when addressed
+          2) Review the current PR diff and flag only clear, high-severity issues
+          3) Leave very short inline comments (1-2 sentences) on changed lines only and a brief summary at the end
+          Procedure:
+          - Get existing comments: gh pr view --json comments
+          - Get diff: gh pr diff
+          - If a previously reported issue appears fixed by nearby changes, reply: ✅ This issue appears to be resolved by the recent changes
+          - Avoid duplicates: skip if similar feedback already exists on or near the same lines
+          Commenting rules:
+          - Max 10 inline comments total; prioritize the most critical issues
+          - One issue per comment; place on the exact changed line
+          - Natural tone, specific and actionable; do not mention automated or high-confidence
+          - Use emojis: 🚨 Critical 🔒 Security ⚡ Performance ⚠️ Logic ✅ Resolved ✨ Improvement
+          Submission:
+          - Submit one review containing inline comments plus a concise summary
+          - Use only: gh pr review --comment
+          - Do not use: gh pr review --approve or --request-changes"