document-decisions

Analyzes uncommitted git changes to identify architectural decisions and generate ADR files.

Updated Jan 11, 2026
One-click install
npx skills add https://github.com/ApolonTorq/m365-mail-mirror --skill document-decisions-apolontorq
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: document-decisions
Source: https://github.com/ApolonTorq/m365-mail-mirror/tree/main/.claude/skills/document-decisions
Command: npx skills add https://github.com/ApolonTorq/m365-mail-mirror --skill document-decisions-apolontorq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Architectural decisions made during development often go undocumented, leaving teams without a record of why key design choices were made. This Skill inspects uncommitted git changes, detects decisions that warrant Architecture Decision Records, and drafts ADR files with minimal user input. ## Core Features & Use Cases - Change Analysis: Runs git diff to categorize modified files by architectural area such as interfaces, entities, configuration, and authentication. - Decision Detection: Applies confidence-ranked heuristics to flag new abstractions, schema changes, dependencies, and patterns worth documenting. - Context Inference: Reads source code, related files, and existing ADRs to draft most of each ADR automatically, asking only for non-inferable context. - Use Case: After implementing a new base command class and a database entity, run this Skill to review the changes, confirm which decisions matter, and produce properly numbered ADR files in the decisions folder. ## Quick Start Analyze my uncommitted git changes and create ADRs for any architectural decisions you find.

Frequently Asked Questions about document-decisions

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

FAQPage Schema
How do I document architectural decisions from git changes?▼

Run this Skill with uncommitted changes present. It runs git diff, categorizes changed files by architectural area, ranks potential decisions by confidence, and drafts ADR files after you confirm which ones to document.

What changes qualify as architectural decisions for an ADR?▼

New abstract classes, interfaces with implementations, database entity changes, new dependencies, authentication changes, and configuration schema changes rank as high confidence. Bug fixes, formatting, and test-only changes are excluded.

Does this Skill work on committed changes?▼

No, it analyzes only uncommitted or staged changes via git diff HEAD. If no uncommitted changes exist, it reports that and exits without creating any ADRs.

How does the Skill avoid duplicate ADRs?▼

It reads all existing files in the decisions folder, parses their titles and content for keywords, and flags potential overlaps with existing ADRs before suggesting new ones.

What information do I need to provide when creating an ADR?▼

The Skill infers context, decision, consequences, and rationale from source code analysis. You only answer questions about non-inferable details like business motivation or rejected alternatives, then approve a preview before the file is written.