adr-gate

Enforce architectural decision linkage for non-trivial code changes before review.

Updated Jun 19, 2026
One-click install
npx skills add https://github.com/lciacci/tessera --skill adr-gate
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: adr-gate
Source: https://github.com/lciacci/tessera/tree/main/skills/adr-gate
Command: npx skills add https://github.com/lciacci/tessera --skill adr-gate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents non-trivial code changes from introducing undocumented architectural decisions, helping teams preserve rationale, maintain review context, and avoid accidental divergence from accepted decisions.

Core Features & Use Cases

  • Change Classification: Distinguishes trivial edits from changes that require architectural decision tracking.
  • Decision Discovery: Finds relevant ADRs, specifications, ticket references, and historical decision context for changed files.
  • ADR Drafting and Review Context: Reverse-engineers Proposed ADRs when no linkage exists, enforces ADR indexing, and injects architectural context into code reviews.
  • Use Case: When a change adds a new service, schema, security surface, or framework pattern, use the gate to identify existing decisions or draft a properly indexed ADR before review or commit.

Quick Start

Run the ADR gate on the current non-trivial changes and present any missing decision records for review.

Frequently Asked Questions about adr-gate

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

FAQPage Schema
How do I enforce architectural decision records are linked before a code commit?▼

You can enforce ADR linkage before commits by running a gate that classifies non-trivial code changes, discovers existing ADRs, and requires decision context injection before review proceeds.

When do I need architectural decision tracking for code changes?▼

Architectural decision tracking is needed when code changes introduce new patterns, services, schemas, security surfaces, or lifecycle mechanisms that alter system structure and require documented rationale.

What happens if a code change has no matching architecture decision record?▼

If no suitable record exists, the gate reverse-engineers a Proposed ADR from the changes and enforces proper indexing before the code review or commit process can continue.

How do I distinguish trivial code edits from changes that require an ADR?▼

The gate performs change classification to automatically distinguish trivial edits from non-trivial changes that require architectural decision tracking and specification discovery.

Can I inject architectural context into code reviews automatically?▼

Yes, the gate injects relevant architectural decision context, historical records, and specification references directly into code reviews to maintain context and prevent divergence from accepted decisions.

How do I stop undocumented architectural decisions from entering the codebase?▼

You can prevent undocumented architectural decisions by applying a pre-commit gate that requires change classification, ADR discovery, and specification linkage for all non-trivial modifications.