adr-commit

ADR-Commit — Finish a Branch with a Decision Record

Completes a development branch with a mandatory ADR gate and PATTERN-DEBT lifecycle review.

Announce: "I'm using adr-commit to complete this work."

---

Step 1: Verify Tests

npm test / cargo test / pytest / go test ./...

Failing tests → stop. Show failures. Do not proceed.

---

Step 2: Detect Environment

GIT_DIR=$(cd "$(git rev-parse --git-dir)" 2>/dev/null && pwd -P)
GIT_COMMON=$(cd "$(git rev-parse --git-common-dir)" 2>/dev/null && pwd -P)

State	Menu	Cleanup
GIT_DIR == GIT_COMMON	4 options	None
GIT_DIR != GIT_COMMON, named branch	4 options	Provenance-based
GIT_DIR != GIT_COMMON, detached HEAD	3 options	None

---

Step 3: Determine Base Branch

git merge-base HEAD main 2>/dev/null || git merge-base HEAD master 2>/dev/null

---

Step 3.5: ADR Gate ← MANDATORY

Cannot proceed to Step 4 without a committed ADR.

# Recent commits for context (auto-injected):
!git log --oneline -10 2>/dev/null

Choose output target:

# DPS present? → append to .dps/spec/ADR.md
# DPS absent?  → standalone file (legacy format, unchanged)
ls .dps/spec/ADR.md 2>/dev/null && echo "DPS mode" || echo "Standalone mode"

DPS ADR format (khi DPS present):

---
## ADR-{{N}}: {{Feature Name}}

<!-- dps:id=ADR-{{N}} -->
<!-- dps:type=adr -->

**DATE:** {{YYYY-MM-DD}}
**STATUS:** ACCEPTED
**CHANGE CLASSIFICATION:** {{DESIGN CHANGE | SPEC BUG | IMPLEMENTATION BUG | INTENT DRIFT | EXTERNAL CONSTRAINT CHANGE}}

### Context
{{What problem forced this decision?}}

### Decision
{{What was built or changed? One concrete paragraph.}}

### Alternatives Considered
{{At least one alternative and why rejected.}}

### Consequences
{{What improved? What worsened? What debt was created?}}

### CONFIDENCE: {{HIGH | MEDIUM | LOW}}
### VOLATILITY: {{STABLE | WATCHFUL | VOLATILE}}
### VALIDATION TARGET: {{Required if CONFIDENCE = LOW}}
### WATCH SIGNAL: {{Required if VOLATILITY = WATCHFUL or VOLATILE}}
### LAST CONFIRMED: {{YYYY-MM-DD}} (INITIAL)

### IMPACT RADIUS
Components: {{list component names from DPS Component Registry}}
Schemas: {{list schema names from DPS CONTRACTS.md}}
Cascade Review: {{✅ Not needed | 🔄 Pending: component/schema list}}

### Evidence (T1/T2)
{{Ran command → output | CI passed | peer confirmed}}

### Part 10: Cycle Retrospective
{{For knowledge-compound: what surprised us, what to do differently}}
---