skills.rest
thrawn01
thrawn01COMMUNITY
Explore all skills by this author →
Website𝕏@thrawn01GitHub

review-behavior-change

Classify diff surface changes as ADR-worthy, CHANGELOG-worthy, or additive.

11|Updated Sep 5, 2025
Search Tags:#testing#documentation#ADR#diff#code-review#CHANGELOG#surface-changes
One-click install
npx skills add https://github.com/thrawn01/claude-dotfiles --skill review-behavior-change
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-behavior-change
Source: https://github.com/thrawn01/claude-dotfiles/tree/main/skills/review-behavior-change
Command: npx skills add https://github.com/thrawn01/claude-dotfiles --skill review-behavior-change

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review recent code changes for undocumented behavioral/surface changes that could affect public interfaces, APIs, or observable behavior, and verify justification against ADRs, PRDs, tech specs, or implementation plans.

Core Features & Use Cases

  • Detects surface-level changes that impact external behavior and public contracts.
  • Classifies changes as ADR-worthy or CHANGELOG-worthy and identifies when changes are purely additive.
  • Generates a protocol-ready report with file paths, severities, and test-impact notes to guide governance.

Quick Start

Run the reviewer on the active diff to identify surface changes and generate a report for review.

Frequently Asked Questions about review-behavior-change

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit code diffs for undocumented behavior changes?▼

Auditing code diffs for undocumented behavior changes involves isolating surface changes that alter public APIs, endpoints, or observable behavior, then classifying them as ADR-worthy, CHANGELOG-worthy, or additive to generate a structured governance report.

How do I classify code review changes for ADRs and CHANGELOGs?▼

Classifying code review changes for ADRs and CHANGELOGs requires analyzing the active diff and related tests to determine if modifications are ADR-worthy, CHANGELOG-worthy, or purely additive, producing a report with file paths and severities.

What is a surface change in API and endpoint code review?▼

A surface change in API and endpoint code review is a modification that alters public interfaces, endpoints, or observable behavior, which must be isolated and verified against existing ADRs, PRDs, or tech specs to ensure proper documentation.

Does behavior change analysis check test impact and affected files?▼

Behavior change analysis checks test impact and affected files by applying isolation logic to the current diff and related tests, outputting a structured report detailing affected file paths, severities, and test-impact notes.

When do I need to generate a governance report for undocumented API changes?▼

Generating a governance report for undocumented API changes is needed when recent code modifications impact external behavior or public contracts, requiring verification against implementation plans to guide documentation and governance.

Can I review active diffs for additive changes versus breaking API changes?▼

Reviewing active diffs for additive changes versus breaking API changes involves classifying each surface change to determine if it is purely additive or alters observable behavior, ensuring ADR-worthy modifications are properly flagged.

Related Skills

Explore More Software Engineering Skills→
huichenhuichen

review

Analyze branch diffs for structural issues and classify plan items.

Community
Advanced
alexandrbasisalexandrbasis
12

udoc

Update project documentation and generate changelog entries from completed tasks.

Community
Intermediate
dhofheinzdhofheinz
9

Commit Analysis Skill

Analyze git diffs to detect commit type, scope, and atomicity.

Community
Intermediate
azmankudusazmankudus

blueprint-webapi

Enforce API contracts using a single OpenAPI 3.1 master specification.

Community
Advanced