developer-hub

Audit a single Harness Developer Hub documentation page for accuracy, completeness, and editorial quality. Produces a scored report (pass/fail) and optionally rewrites the page. Triggers: "audit [file-path]", "audit [url]", "doc audit", "check this doc", "score this page", "audit the oldest page in [module]", or any request to evaluate a single documentation page against the Harness quality rubric. Also triggers when the user provides a developer.harness.io URL and asks for feedback or a JIRA ticket. For a full audit that also crawls every sibling page in the section, use doc-section-audit instead.

Write, rewrite, or review a best-practices documentation page in any module so it reads like advice from an experienced practitioner, not a feature tour. Enforces the recommendation + rationale + consequence model and the must-not rules (no "What you will learn", no Troubleshooting, no concept dumps). Triggers: "best practices page", "X best practices", "write best practices for", "is this a good best practices page", "review this best practices doc", "score this best practices page", or any request to create or update a page whose job is to recommend what to do and warn what breaks if you do not.

Score every page in a Harness Developer Hub module for compliance with the Claude and cursor rules, doc-structure template, and HDH writing style. Produces a module-level compliance report ranked by severity. Triggers: "module audit [module]", "compliance check [module]", "score all docs in [module]", "doc-module-audit [module]", "doc-module-check [module]", or any request to audit quality or style compliance across all pages in a module.

Audit a Harness Developer Hub documentation page and its entire sibling section. Scores the target page, crawls every sibling in the same folder, produces a section-level verdict and consolidation plan, and outputs a JIRA ticket description and rewrite prompt. Triggers: "section audit [file-path]", "audit [module] section", "audit the full section", "doc section audit", or any request that calls for auditing a page AND its surrounding docs. For a single-page audit without section crawl, use doc-audit instead.

Rewrite a single Harness Developer Hub documentation page based on an existing audit report. Reads the audit findings and applies all suggested improvements to the page. Triggers: "rewrite [file-path]", "apply the audit", "fix the doc", "doc rewrite [file]", or any request to apply audit findings to a page. Requires a prior doc-audit report to exist. For section-wide rewrites, use doc-section-rewrite instead.

Apply a doc-section-audit report across an entire section in supervised phases. Reads the audit findings and executes structural changes (Phase 1), content rewrites (Phase 2), and redirect/cleanup work (Phase 3), pausing for a git diff review between each phase. Triggers: "section rewrite [audit-report]", "apply the section audit", "execute the rewrite plan", "doc section rewrite", or any request to apply a doc-section-audit report to files in the repo.

Identify the most overdue documentation in a module and recommend whether each candidate warrants a single-page audit or a full section audit. Produces a ranked triage report. Triggers: "audit check [module]", "what needs auditing in [module]", "find stale docs in [module]", "doc audit check [module]", "where should I start with [module] docs", or any request to prioritise which pages in a module to audit next.

Extended documentation review for non-Harness docs or when image/link/SEO validation is needed. Use for: external repos, README reviews, blog posts, tutorial audits where asset validation matters. Adds: image path/alt-text/freshness checks, cross-reference validation, factual verification via web search, SEO/AEO analysis, What-Why-How framework evaluation. For Harness DevHub docs, use doc-section-audit instead (includes Harness-specific scoring and JIRA generation).