Add doc parity to review agent

.claude-plugin/marketplace.json

@@ -24,7 +24,7 @@
     {
       "name": "bitwarden-code-review",
       "source": "./plugins/bitwarden-code-review",
-      "version": "1.13.1",
+      "version": "1.14.0",
       "description": "Comprehensive code review system with organization-wide standards."
     },
     {

README.md

@@ -10,7 +10,7 @@ A curated collection of plugins for AI-assisted development at Bitwarden. Enable
 | [bitwarden-tech-lead](plugins/bitwarden-tech-lead/)                 | 3.0.0   | Tech lead for technical planning, architecture coherence, and surfacing patterns to Technical Strategy Ideas                                                |
 | [bitwarden-shepherd](plugins/bitwarden-shepherd/)                   | 1.0.1   | Champion of a technical strategy — shepherds a TSI through evaluation into the funnel, then through to adoption                                             |
 | [bitwarden-atlassian-tools](plugins/bitwarden-atlassian-tools/)     | 2.4.0   | Read-only Atlassian access via MCP server with deep Jira issue research skill                                                                               |
-| [bitwarden-code-review](plugins/bitwarden-code-review/)             | 1.13.1  | Autonomous code review agent following Bitwarden engineering standards with GitHub integration                                                              |
+| [bitwarden-code-review](plugins/bitwarden-code-review/)             | 1.14.0  | Autonomous code review agent following Bitwarden engineering standards with GitHub integration                                                              |
 | [bitwarden-delivery-tools](plugins/bitwarden-delivery-tools/)       | 2.4.0   | Delivery lifecycle skills: initiative funnel navigation, work transitions, tech breakdowns and task decomposition, commits, PRs, preflight, labeling        |
 | [bitwarden-designer](plugins/bitwarden-designer/)                   | 0.1.0   | Product designer persona: Code of Conduct and 30/60/90 critique, critique facilitation; dispatches into bitwarden-design-tools                              |
 | [bitwarden-design-tools](plugins/bitwarden-design-tools/)           | 0.1.0   | Design toolkit: content style guide, Figma Dev Mode MCP, Bitwarden brand application, handoff prep, Design System governance, Product and Design Jira       |

plugins/bitwarden-code-review/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "bitwarden-code-review",
-  "version": "1.13.1",
+  "version": "1.14.0",
   "description": "Comprehensive code review system with organization-wide standards.",
   "author": {
     "name": "Bitwarden",

plugins/bitwarden-code-review/CHANGELOG.md

@@ -5,6 +5,12 @@ All notable changes to the Bitwarden Code Review Plugin will be documented in th
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [1.14.0] - 2026-08-07
+
+### Added
+
+- Documentation-parity review enrichment. When the diff touches any code with a documented ancestor scope (a `README.md`, `docs/` directory, or source-embedded doc comments in the change's ancestor chain), the `bitwarden-code-reviewer` agent now invokes `Skill(verifying-doc-parity)` during Cross-Plugin Enrichment to run the documentation pass — verify or update in-repo docs at every documented ancestor scope of the change, and discover out-of-repo pages the change invalidates. The dependency on the `bitwarden-doc-parity` plugin is optional; if it is not installed in the review environment, the review falls back to existing review knowledge.
+
 ## [1.13.1] - 2026-07-01
 
 ### Changed

plugins/bitwarden-code-review/agents/bitwarden-code-reviewer/AGENT.md

@@ -1,6 +1,6 @@
 ---
 name: bitwarden-code-reviewer
-version: 1.13.0
+version: 1.14.0
 description: Conducts thorough code reviews following Bitwarden standards. Finds all issues first pass, avoids false positives, respects codebase conventions. Invoke when user mentions "code review", "review code", "review", "PR", or "pull request".
 model: opus
 skills: avoiding-false-positives, classifying-review-findings, posting-bitwarden-review-comments, posting-review-summary, reviewing-dependency-changes
@@ -82,6 +82,10 @@ When sibling Bitwarden plugins are installed, activate specialist skills during
 
 - invoke `Skill(reviewing-claude-config)` to validate YAML frontmatter, progressive-disclosure structure, prompt-engineering quality, and config-specific security issues (committed `settings.local.json`, hardcoded secrets, broken file references, overly broad agent tool access). Fold its findings into your own classification and validation in Steps 3–4.
 
+**Documentation parity** (any code change with a documented ancestor scope — a `README.md`, `docs/` directory, or source-embedded doc comments in the change's ancestor chain — which covers most substantive PRs):
+
+- invoke `Skill(verifying-doc-parity)` to run the documentation pass in review context: identify drifted in-repo docs at every documented ancestor scope of the change, and discover out-of-repo pages the change invalidates. Report drift as findings — do not edit files in the PR — and fold them into your classification and validation in Steps 3–4, applying the documentation standard's external-docs flow (work item before merge, stale marker on the page) when applicable.
+
 These skills are optional. If unavailable, apply existing review knowledge.
 
 **Before moving to Step 3**, confirm you've examined all changed code for the above issues.