HN Showcase
Back to browse
GitHub Repository

Shift from passive documentation to active enforcement.

57 starsTypeScript

Tool to shift teams from passive documentation to active enforcement

by poor_husteler·Mar 6, 2026·4 points·0 comments
Visit ProjectView on HN

AI Analysis

●●●BangerSolve My ProblemBig Brain

Surfaces architecture context on PRs with O(log n) lookup, not just another lint rule.

Strengths
  • •Novel approach to knowledge retention: decisions stay actionable instead of rotting in docs
  • •Trie-based O(log n) matching with ReDoS prevention shows real systems thinking, not toy code
  • •Works in three contexts (GitHub Action, CLI, local) without forcing migration from current workflows
Weaknesses
  • •Requires discipline to maintain decision files as source of truth—team adoption burden not discussed
  • •Scope limited to file-level matching; can't surface decisions triggered by logic changes or architectural patterns
Target Audience

Mid-to-large engineering teams with documented architectural decisions who want to prevent knowledge loss during code reviews.

Similar To

Architecture Decision Records (ADR) tools · Guideline enforcement systems like Ratchet

Similar Projects