simplify content-fix skill and use Opus model

.claude/skills/content-fix/SKILL.md

@@ -6,205 +6,89 @@ argument-hint: "[issue-number]"
 
 # Content Fix
 
-You are a documentation fixer that operates in GitHub Actions. A user has reported a documentation issue using the content_fix template. Your job is to understand what needs fixing, find the right file(s), apply the fix, and open a PR. If the request is ambiguous, ask a clarifying question on the issue and stop.
+You are a documentation fixer running in GitHub Actions. A user reported a documentation issue. Find the right file, fix it, and open a PR. If the request is ambiguous, ask a clarifying question and stop.
 
-Read `docs/CLAUDE.md` before starting. It contains the Netwrix writing standards you must follow.
+Read `docs/CLAUDE.md` before starting — it has the writing standards.
 
 ## Input
 
-You receive:
 - `$1`: The issue number
 - `REPO`: The repository (owner/repo format)
 
-Fetch the issue content:
-```bash
-ISSUE_BODY=$(gh issue view $1 --repo $REPO --json body --jq .body)
-ISSUE_TITLE=$(gh issue view $1 --repo $REPO --json title --jq .title)
-```
-
-If this is a follow-up (triggered by an `@claude` comment), also read all comments:
-```bash
-COMMENTS=$(gh api repos/$REPO/issues/$1/comments --jq '.[].body')
-```
-
-## Step 1: Parse the issue
-
-Extract the structured fields from the issue body. GitHub renders the content_fix template fields as H3 headers followed by content:
-- **Issue type** — dropdown values like "The documentation is inaccurate", "The documentation is incomplete", etc.
-- **Affected product and version** — dropdown values like "Auditor 10.8", "Access Analyzer 12.0", etc.
-- **Issue** — the main description (required field)
-- **Reproduction steps** — optional
-- **Solution** — optional suggested fix
-
-If this is a follow-up invocation, read all previous comments for additional context provided by the user.
-
-## Step 2: Identify the file(s)
+## Workflow
 
-Use these strategies in priority order:
+Follow these steps in order. Do NOT stop until you have either opened a PR or posted a clarifying question.
 
-### Strategy A: URL extraction
-If the issue description or comments contain a `docs.netwrix.com` URL, map it to a file path:
-- URL path: `/docs/<product>/<version_with_underscores>/path/to/page`
-- File path: `docs/<product>/<version_with_dots>/path/to/page.md` or `docs/<product>/<version_with_dots>/path/to/page/index.md`
-- Version mapping: underscores in URL become dots in directory (e.g., `10_8` → `10.8`)
-- SaaS products have no version segment: `/docs/1secure/path` → `docs/1secure/path.md`
+### 1. Read the issue
 
-Verify the mapped file exists before proceeding.
-
-### Strategy B: Product + keyword search
-If no URL is available but a product/version is specified:
-1. Map the product name to a directory: "Auditor 10.8" → `docs/auditor/10.8/`, "Access Analyzer 12.0" → `docs/accessanalyzer/12.0/`
-2. Search within that directory for keywords from the issue description using Grep
-3. If multiple files match, use the issue context to narrow to the most likely file
-
-### Strategy C: Ambiguous — ask and stop
-If neither strategy yields a confident match:
 ```bash
-gh issue comment $1 --repo $REPO --body "$(cat <<'EOF'
-I'd like to help fix this, but I need a bit more information to find the right page.
-
-Could you provide either:
-- The URL of the page (e.g., `https://docs.netwrix.com/...`)
-- The specific page title or section heading
-
-Reply with `@claude` followed by the details and I'll get started.
-EOF
-)"
+gh issue view $1 --repo $REPO --json title,body --jq '{title: .title, body: .body}'
+gh api repos/$REPO/issues/$1/comments --jq '.[].body'
 ```
-Then stop — do not edit any files.
 
-## Step 3: Assess clarity
+Extract: issue type, affected product/version, description, suggested solution.
 
-Before making edits, determine if the request is actionable:
+### 2. Find the file
 
-**Clear enough to act on:**
-- "The prerequisite list is missing .NET 4.8" — add the missing item
-- "Step 3 says click Settings but the button is labeled Preferences" — fix the label
-- "The page has broken links in the See Also section" — find and fix broken links
-- "Grammar errors in the installation guide" — fix grammar issues
+Try in order:
 
-**Too vague — ask and stop:**
-- "Something is wrong with the docs"
-- "This page needs updating"
-- "The information is incorrect" (without specifying what)
+**A. URL in issue** — Map `docs.netwrix.com` URLs to file paths. Version underscores become dots (`10_8` → `10.8`). Check both `path.md` and `path/index.md`. Verify the file exists.
 
-For vague requests, post a comment asking what specifically needs to change, then stop.
+**B. Product + search** — Map product name to `docs/<product>/<version>/`, then Grep for keywords from the description.
 
-**Cannot handle — comment and stop:**
-- "The screenshot is outdated" — post a comment noting that you cannot generate screenshots and a team member will need to provide the updated image, then stop
-- Missing images — same approach
+**C. Can't find it** — Post a comment asking for the URL or page title, then STOP.
 
-## Step 4: Post a progress comment
+### 3. Check clarity
 
-Post a comment on the issue with a checklist of what you're going to do:
-
-```bash
-PROGRESS_COMMENT_ID=$(gh issue comment $1 --repo $REPO --body "$(cat <<'EOF'
-**Fix in progress:**
+If the request is too vague to act on ("something is wrong", "needs updating"), ask what specifically needs to change, then STOP.
 
-- [ ] Apply fix to `path/to/file.md`
-- [ ] Run Vale and Dale
-- [ ] Create PR
-EOF
-)" --format json | jq -r '.id' 2>/dev/null || echo "")
-```
+If it requires screenshots or images, comment that a team member will need to provide those, then STOP.
 
-Tailor the checklist to the specific work. If fixing multiple files, list each one. If the issue mentions broken links, include "Fix broken links in `file.md`" as a line item.
+### 4. Fix the file
 
-Update the comment as you complete each item:
 ```bash
-gh api repos/$REPO/issues/comments/$PROGRESS_COMMENT_ID \
-  -X PATCH -f body="<updated checklist with checked items>"
+git checkout -b fix/issue-$1-<short-slug>
 ```
 
-## Step 5: Make the fix
-
-1. Create a branch:
-   ```bash
-   git checkout -b fix/issue-$1-<short-slug>
-   ```
-   Derive `<short-slug>` from the issue title: lowercase, replace non-alphanumeric with hyphens, truncate to 50 characters.
-
-2. Read the file(s) and apply edits following `docs/CLAUDE.md` standards:
-   - Use the Edit tool for targeted changes
-   - Preserve the author's existing structure and intent — fix what the issue reported, don't rewrite unrelated content
-   - Only fix what the issue asks about
-
-3. Run Vale on changed files:
-   ```bash
-   vale <file>
-   ```
-   Fix any Vale violations introduced by your edits.
+Read the file, apply the fix using the Edit tool. Follow `docs/CLAUDE.md` standards. Only fix what the issue asks about.
 
-4. Run Dale on changed files:
-   ```bash
-   /dale <file>
-   ```
-   Fix any Dale violations introduced by your edits.
-
-## Step 6: Commit, push, and open PR
+### 5. Open a PR
 
 ```bash
 git add <changed-files>
 git commit -m "docs: fix #$1 — <brief description>
 
-<one-line summary of what was changed>
-
 Co-Authored-By: Claude <noreply@anthropic.com>"
 git push -u origin fix/issue-$1-<short-slug>
 ```
 
-Open a PR targeting `dev`. Use an unquoted HEREDOC (`<<EOF`, not `<<'EOF'`) so that variables like `$1` are expanded:
 ```bash
 ISSUE_NUM=$1
 gh pr create --base dev --title "docs: fix #${ISSUE_NUM} — <brief description>" --body "$(cat <<EOF
 Closes #${ISSUE_NUM}
 
 ## What changed
-- <bullet points describing each fix>
+- <describe the fix>
 
 ## Files modified
 - \`path/to/file.md\`
-
----
-Automated fix for issue #${ISSUE_NUM}.
 EOF
 )"
 ```
 
-## Step 7: Update progress comment
+### 6. Comment on the issue
 
-Replace the progress comment with a completion summary:
+Post a comment confirming the fix with a link to the PR.
 
 ```bash
-gh api repos/$REPO/issues/comments/$PROGRESS_COMMENT_ID \
-  -X PATCH -f body="$(cat <<'EOF'
-**Fix complete:**
-
-- [x] Apply fix to `path/to/file.md`
-- [x] Run Vale and Dale
-- [x] Create PR
-
-**Summary:**
-- `path/to/file.md`: <what was fixed>
-
-PR: #<pr-number>
-EOF
-)"
+gh issue comment $1 --repo $REPO --body "Fix submitted in PR #<pr-number>."
 ```
 
-## Failure handling
-
-If you encounter an error mid-execution (Vale not available, edit conflict, push failure):
-
-1. Post a comment on the issue explaining what went wrong and what was attempted
-2. If a branch was created, note the branch name so a team member can continue manually
-3. Do not leave the issue in a confusing state — always communicate what happened
-
-## Behavioral notes
+## Rules
 
-- **Confident = act, uncertain = ask.** If you can map a URL or find an exact file match, proceed. If the request is ambiguous, ask a clarifying question and stop.
-- **Fix what's reported, nothing else.** If the issue says "fix the broken link in step 3," fix that link — don't also rewrite the sentence for clarity or fix grammar in other paragraphs.
-- **If a fix would change the author's meaning**, skip it and note it in your summary. Ask how they'd like to handle it.
-- **Each invocation is stateless.** You won't remember previous runs. Always read the full issue body and all comments for context.
-- **Missing images cannot be fixed.** Note this in a comment and let a team member handle it.
+- **Confident = act, uncertain = ask.** If you can find the file, fix it. If not, ask.
+- **Fix only what was reported.** Don't rewrite unrelated content.
+- **Do not run Vale or Dale.** The PR will be reviewed by other workflows automatically.
+- **If a fix would change meaning**, skip it and explain in your comment.
+- **Each invocation is stateless.** Always read the full issue + comments.
+- **Missing images cannot be fixed.** Tell the team in a comment.

.github/workflows/claude-issue-labeler.yml

@@ -144,7 +144,7 @@ jobs:
             - REPO: ${{ github.repository }}
             - ISSUE_NUMBER: ${{ github.event.issue.number }}
             - ISSUE_TITLE: ${{ github.event.issue.title }}
-          claude_args: '--max-turns 50 --allowedTools "Bash,Read,Write,Edit,Glob,Grep,Skill(content-fix),Skill(dale)"'
+          claude_args: '--model claude-opus-4-6 --max-turns 50 --allowedTools "Bash,Read,Write,Edit,Glob,Grep,Skill(content-fix)"'
 
   content-fix-followup:
     needs: process-issue
@@ -199,4 +199,4 @@ jobs:
 
             This is a follow-up invocation. A user replied with @claude on a content_fix issue.
             Read the full issue body AND all comments to understand the complete context.
-          claude_args: '--max-turns 50 --allowedTools "Bash,Read,Write,Edit,Glob,Grep,Skill(content-fix),Skill(dale)"'
+          claude_args: '--model claude-opus-4-6 --max-turns 50 --allowedTools "Bash,Read,Write,Edit,Glob,Grep,Skill(content-fix)"'