skills.rest
erosDiffusion
erosDiffusionCOMMUNITY
Explore all skills by this author →
GitHub

code-reviewer

Analyze codebases and generate standardized per-commit documentation.

3|Updated Jan 20, 2026
Search Tags:#automation#git#documentation#analysis#code-review#version-control#commit-diff
One-click install
npx skills add https://github.com/erosDiffusion/ComfyUI-Erosdiffusion-LTX2 --skill code-reviewer-erosdiffusion
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-reviewer
Source: https://github.com/erosDiffusion/ComfyUI-Erosdiffusion-LTX2/tree/main/.agent/skills/code-reviewer
Command: npx skills add https://github.com/erosDiffusion/ComfyUI-Erosdiffusion-LTX2 --skill code-reviewer-erosdiffusion

SYSTEM DOCUMENTATION & REQUIREMENTS

## What problem does it solve? Monitor codebase changes and generate standardized per-commit analysis documentation to help teams track changes, decisions, and potential risks. ## Core Features & Use Cases

  • Automatic per-commit documentation outlining architecture changes, features, regressions, and breaking changes.
  • Consistent templates and folder structure (bot-analysis/ with INDEX.md and commits/NN_XXXX.md) for easy navigation. ### Quick Start Run the code-reviewer workflow to generate per-commit documentation for new commits.

Frequently Asked Questions about code-reviewer

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

FAQPage Schema
How do I automatically generate per-commit documentation for git changes?▼

Automate per-commit documentation by analyzing a codebase to outline architecture changes, features, regressions, and breaking changes. This process monitors new commits across branches and development sessions to capture decisions and potential risks.

How does per-commit analysis handle version control output structure?▼

Per-commit analysis structures version control output deterministically. It generates standardized reports organized within a bot-analysis/ directory, containing an INDEX.md file and individual commit files in a commits/ subfolder.

Can I use automated code review to monitor new commits across multiple branches?▼

Automated code review can monitor new commits across multiple branches and development sessions. It analyzes the codebase continuously to capture and document architecture changes, features, regressions, and breaking changes.

What is the best way to track breaking changes and regressions in a codebase?▼

Tracking breaking changes and regressions effectively requires standardized per-commit analysis. This approach automatically monitors codebase changes across branches, generating consistent documentation for easy navigation and risk tracking.

How do I start automating commit diff analysis for my project?▼

Automating commit diff analysis starts by running the workflow to generate per-commit documentation for new commits. The process applies consistent templates to analyze the codebase and outputs organized reporting in a fixed folder structure.

Related Skills

Explore More Software Engineering Skills→
ZESCODEZESCODE

GitCrawl ZES

Search git commit logs and inspect code patterns across ZES system repositories.

Community
Basic
orekyuuorekyuu

junit-report-collector

Collect JUnit XML test reports and summarize pass, fail, and skip results.

Community
Intermediate
zerAdazerAda

bmad-qa-generate-e2e-tests

Generate end-to-end API and UI tests for identified application features.

Community
Advanced
FaysilAlshareefFaysilAlshareef
4

changelog-gen

Generate changelogs from git commits using Conventional Commits and Keep a Changelog formats.

Community
Intermediate