adr-review

Included with Lifetime

$97 forever

Review code changes against accepted ADRs for compliance violations

Code Review

What this skill does


# ADR Review

Review code changes against accepted Architecture Decision Records to detect violations, drift, and non-compliance.

## When to use

Before merging a PR, after significant code changes, or as part of a periodic compliance check. Use this to ensure code changes respect the architectural decisions the team has agreed upon.

## Steps

1. **Get diff** -- Run `git diff main...HEAD --name-only` (or the specified branch) to list changed files. Then run `git diff main...HEAD` to get the full diff content.

2. **Find relevant ADRs** -- For each changed file:
   - `Grep` the file for ADR references (`ADR-\d+`)
   - `Grep` `docs/adr/` for ADRs that mention the changed file paths or modules
   - Call `mcp__claude-flow__memory_search` with the file path and change summary to find semantically related ADRs

3. **Load ADR content** -- `Read` each relevant ADR file. Focus on:
   - The **Decision** section (what was decided)
   - The **Status** (only enforce "accepted" ADRs)
   - The **Consequences** (expected constraints)

4. **Check for violations** -- Analyze each changed file against its relevant ADRs:
   - Does the code change contradict an accepted decision?
   - Does it use a technology/pattern that an ADR explicitly rejected?
   - Does it modify a module in a way the ADR's consequences warned against?
   - Is the code referencing a deprecated or superseded ADR?

5. **Query relationship graph** -- Call `mcp__claude-flow__agentdb_causal-query` to check if any referenced ADRs have been superseded. If so, flag that the code references an outdated decision.

6. **Report** -- Present findings as a compliance report:
   ```
   ## ADR Compliance Report

   ### Violations
   - [ ] <file>:<line> — violates ADR-NNN: <reason>

   ### Warnings
   - [!] <file> references superseded ADR-NNN (replaced by ADR-MMM)

   ### Compliant
   - [x] <file> — consistent with ADR-NNN

   ### Unlinked Changes
   - [?] <file> — no ADR coverage (consider creating one)
   ```

7. **Suggest actions** -- For each violation, suggest whether to update the code or propose a new ADR to supersede the violated one.

Files: 1

Size: 2.4 KB

Complexity: 9/100

Category: Code Review

Source: https://github.com/ruvnet/claude-flow/tree/main/plugins/ruflo-adr/skills/adr-review

Related in Code Review

gstack

Included

Fast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)

Code Reviewscriptsfeatured

startup-due-diligence

Included

Legal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.

Code Reviewscripts

interview-master

Included

This skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.

Code Reviewscripts

fix-issue

Included

Fixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.

Code Reviewscripts

sf-apex

Included

Generates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.

Code Reviewscripts

swift-development

Included

Comprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.

Code Reviewscripts