code-review-docs

Detect conflicts between code-convention.yaml and adr.yaml files.

Updated Jun 5, 2026
One-click install
npx skills add https://github.com/KangJiSseok/ACODIAN --skill code-review-docs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review-docs
Source: https://github.com/KangJiSseok/ACODIAN/tree/main/.codex/skills/code-review-docs
Command: npx skills add https://github.com/KangJiSseok/ACODIAN --skill code-review-docs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Consistency drift between ADR decisions and coding-convention docs across modules can cause conflicting guidance and brittle change workflows.

Core Features & Use Cases

  • Detects conflicts between docs/{module}/code-convention.yaml and docs/{module}/adr.yaml.
  • Proposes targeted reconciliations and chained edits to maintain alignment across ADRs and conventions.
  • Supports batch analysis for multiple modules and provides prioritized change proposals.

Quick Start

To begin, specify the module and the target update (convention, adr, or both) to generate change proposals.

Frequently Asked Questions about code-review-docs

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

FAQPage Schema
How do I detect conflicts between ADRs and coding conventions in YAML files?

To detect conflicts between ADRs and coding conventions, specify a target module like api or web to compare docs/{module}/code-convention.yaml against docs/{module}/adr.yaml. The analysis identifies consistency drift and generates structured proposals detailing required and recommended changes.

What is consistency drift between architecture decision records and convention docs?

Consistency drift occurs when ADR decisions and coding-convention docs provide conflicting guidance across modules. This misalignment causes brittle change workflows and conflicting development instructions, requiring targeted reconciliations and chained edits to maintain alignment.

How do I generate change proposals for updating code conventions and ADRs?

Generate change proposals by specifying the module and the target update, choosing either convention, adr, or both. The process outputs a structured proposal set detailing MUST and RECOMMENDED changes, including rationale and impact for both YAML files.

Can I analyze multiple modules like api, web, infra, and ai for convention drift at once?

Yes, batch analysis is supported for multiple modules including api, web, infra, and ai. The process provides prioritized change proposals to maintain alignment across ADRs and conventions for all specified modules.

Why do my code-convention.yaml and adr.yaml files show conflicting guidance across modules?

Conflicting guidance arises when ADR decisions and code convention YAML files are not synchronized during updates. Identifying these conflicts requires comparing both files per module to propose targeted reconciliations and chained edits.

What is the best way to maintain alignment between ADRs and coding conventions?

The best way to maintain alignment is to perform automated conflict detection between ADR and convention YAML files, then apply prioritized change proposals with structured rationale to ensure both documents remain synchronized across modules.