diff --git a/.claude/skills/doc-pr/SKILL.md b/.claude/skills/doc-pr/SKILL.md
index 3c7d94e8c0..868b1ef851 100644
--- a/.claude/skills/doc-pr/SKILL.md
+++ b/.claude/skills/doc-pr/SKILL.md
@@ -12,11 +12,17 @@ Read `docs/CLAUDE.md` before starting — it contains the writing standards and
 
 ## Input
 
-You receive two arguments:
-- `$1`: A comma-separated list of changed markdown file paths (e.g., `docs/accessanalyzer/12.0/install.md,docs/auditor/10.0/overview.md`)
-- `$2`: The PR number
+Get the file list, PR number, and repo from environment variables:
 
-If arguments are missing, use `gh pr view` and `gh pr diff` to determine the changed files and PR number from the current branch context.
+```bash
+echo "Files: $DOC_PR_FILES"
+echo "PR: $DOC_PR_NUMBER"
+echo "Repo: $DOC_PR_REPO"
+```
+
+If the environment variables are empty, check for positional arguments (`$1` = files CSV, `$2` = PR number). If those are also missing, use `gh pr view` and `gh pr diff` to determine the changed files and PR number from the current branch context.
+
+Split the comma-separated file list into individual file paths for processing.
 
 ## Stage 1: Vale Linting
 
@@ -42,7 +48,7 @@ Dale returns a table of rule violations or a clean report. Collect all Dale outp
 
 This stage applies the doc-help editing analysis to the PR changes — but non-interactively. You are producing a written review, not having a conversation.
 
-1. Run `gh pr diff $PR_NUMBER` to get the diff
+1. Run `gh pr diff $DOC_PR_NUMBER` to get the diff
 2. For each changed file, read the full file content
 3. Analyze ONLY the added or modified lines (lines starting with `+` in the diff) against these four priorities:
 
@@ -62,9 +68,13 @@ For each issue found, note:
 
 Only report issues on lines that were added or modified in this PR. Do not flag preexisting issues.
 
-## Output
+## Output — MANDATORY: Post as PR Comment
+
+After completing all three stages, you MUST write the review to a file and post it as a PR comment. This is the most important step — the review is useless if it is not posted.
 
-After completing all three stages, post the review as a PR comment using `gh pr comment`. Build the comment body following this structure:
+**Step 1: Write the review to a temporary file.**
+
+Write the full review body to `/tmp/doc-pr-review.md` using the Write tool. Follow this structure:
 
 ```markdown
 ## Documentation PR Review
@@ -119,17 +129,13 @@ You can ask Claude anything about the review or about Netwrix writing standards.
 > Automated fixes are only available for branches in this repository, not forks.
 ```
 
-Post the comment with:
+**Step 2: Post the comment.**
 
 ```bash
-gh pr comment $PR_NUMBER --repo $REPO --body "$REVIEW_BODY"
+gh pr comment $DOC_PR_NUMBER --repo $DOC_PR_REPO --body-file /tmp/doc-pr-review.md
 ```
 
-Use a heredoc or temporary file to avoid shell escaping issues with the multi-line body. For example:
-
-```bash
-gh pr comment $PR_NUMBER --repo $REPO --body-file /tmp/doc-pr-review.md
-```
+If the `gh pr comment` command fails, report the error. Do NOT end your turn without attempting to post.
 
 ## Behavioral Notes
 
diff --git a/.github/workflows/claude-doc-pr.yml b/.github/workflows/claude-doc-pr.yml
index 479b1d2050..d24d601af1 100644
--- a/.github/workflows/claude-doc-pr.yml
+++ b/.github/workflows/claude-doc-pr.yml
@@ -27,6 +27,7 @@ jobs:
         uses: actions/checkout@v4
         with:
           ref: ${{ github.event.pull_request.head.sha }}
+          fetch-depth: 1
 
       - name: Get changed markdown files
         id: changed-files
@@ -89,18 +90,28 @@ jobs:
         uses: anthropics/claude-code-action@v1
         env:
           GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          DOC_PR_REPO: ${{ github.repository }}
+          DOC_PR_NUMBER: ${{ github.event.pull_request.number }}
+          DOC_PR_FILES: ${{ steps.changed-files.outputs.files }}
         with:
           anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
           github_token: ${{ secrets.GITHUB_TOKEN }}
           show_full_output: true
           prompt: |
-            Call the doc-pr review skill:
-            /doc-pr ${{ steps.changed-files.outputs.files }} ${{ github.event.pull_request.number }}
+            You are a documentation reviewer. Run /doc-pr to review this PR, then post the results as a PR comment.
 
-            Context:
-            - REPO: ${{ github.repository }}
-            - PR_NUMBER: ${{ github.event.pull_request.number }}
-            - CHANGED_FILES: ${{ steps.changed-files.outputs.files }}
+            Environment variables are set:
+            - DOC_PR_REPO=${{ github.repository }}
+            - DOC_PR_NUMBER=${{ github.event.pull_request.number }}
+            - DOC_PR_FILES=${{ steps.changed-files.outputs.files }}
+
+            Steps:
+            1. Invoke the doc-pr skill: /doc-pr
+            2. Follow the skill instructions to run Vale, Dale, and editorial review
+            3. CRITICAL: You MUST post the review as a PR comment by running:
+               gh pr comment $DOC_PR_NUMBER --repo $DOC_PR_REPO --body-file /tmp/doc-pr-review.md
+
+            Your task is NOT complete until the gh pr comment command has been executed successfully.
           claude_args: '--allowedTools "Bash,Read,Write,Glob,Grep,Skill(doc-pr),Skill(dale)"'
 
       - name: Debug post-review