Build kb-pr-open Claude Code skill for TSE KB PR workflow

[hilram7]

Build a Claude Code skill (/kb-pr-open) that TSEs can use to review their KB article(s) against quality standards (Vale + Dale + Derek) and create a PR for submission.

Goal: By the time a PR reaches the reviewer, it should need minimal to no content or formatting fixes.

Skill flow:

1. Validate context (repo root, branch safety)
2. Run Vale + Dale + Derek checks on each file
3. Present findings report
4. Apply fixes with author approval
5. Prompt for local testing
6. Stage and commit (Claude does it or provides copy/paste commands)
7. Push and create PR (same choice)

Testing plan: Build locally first, test on Change Tracker KB revisions, iterate, then commit to repo.

Related:

• kb-pr-review skill (reviewer-side counterpart)
• Change Tracker KB Revision Project (docs-kb-staging Pg4ns/release 7.7.5 #64)
• Planning doc: KB-Operations-Notes/General KB Revision Projects/kb-pr-open-skill-plan.md

[hilram7]

Status update — June 15, 2026

The skill is built and matches the original spec.

First end-to-end run completed on the PPE RSA MFA article (docs/kb/passwordpolicyenforcer/authentication-and-integration/set-up-netwrix-password-policy-enforcer-to-work-with-rsa-mfa.md): Vale + Dale + Derek lint → fixes → PR opened → approved → merged. No skill changes came out of the run.

Canonical location: user-global at ~/.claude/skills/kb-pr-open/ for now (private). The original testing plan called for the Change Tracker KB Revision Project as the first fixture; the PPE RSA MFA article was substituted as the active in-flight article at the time.

Sibling skill: kb-writer now exists and owns content coaching — targeted questions about gaps, depth, and clarity, with no style or formatting work. kb-pr-open stays focused on last-mile lint and submission.

Next phase: Breadth testing on paths the first run didn't exercise. An 11-scenario test matrix is documented in the planning doc (KB-Operations-Notes/General KB Revision Projects/kb-pr-open-skill-plan.md → Remaining Test Matrix), covering branch guard, dirty-lint inputs, article-type coverage (Symptom, Error Resolution, Q&A), multi-file invocation, Option B self-serve path, new-article flow, and all-clean pass-through.

Publishing to docs/.claude/skills/ is deferred until breadth testing is stable.