Product documentation

ADR Guard keeps architecture judgment with people while automating repeatable document checks. Start with the CLI, then add only the integrations your workflow needs.

Interfaces

Interface	Use it when	Trust and execution boundary
CLI	You need the complete local command surface	Runs locally with explicit arguments and configuration
GitHub Action	Pull requests should validate or review ADR changes	Runs in GitHub Actions with workflow permissions and pinned inputs
VS Code extension	Contributors want explorer, commands, and diagnostics in the editor	Workspace-hosted; trusted local file workspaces only; invokes an existing CLI
Container	You want an isolated, reproducible CLI runtime	Mount only required files and pass configuration deliberately
Agent Skills	You want a coding agent to guide ADR decisions and CLI workflows	Portable agent instructions; no bundled CLI or automatic architectural approval

Core workflows

• Create canonical ADRs with Minimal, Extended, or constrained custom templates.
• Validate relationships, changed files, and diagnostic baselines.
• Produce machine-readable and human-readable reports.
• Opt into AI-assisted drafting or review with explicit providers and security controls.
• Validate MADR 4.0 documents in a separate opt-in mode.

AI and human confirmation

Drafting and review send selected context to the configured provider. Provider output is untrusted, bounded, parsed, and presented for human evaluation. It does not approve decisions, edit accepted history automatically, or replace security and architecture review.

MCP status

The repository does not currently publish a standalone ADR Guard MCP server. Do not configure or depend on one based on this portal. The supported public surfaces are the CLI, GitHub Action, container, and VS Code extension documented here.

For command-level details, use the CLI reference and preserve the actual installed version when troubleshooting.