architectural-decisions
OfficialTrace design rationale across your code.
Software Engineering#architecture#documentation#decisions#codebase#architectural#design-rationale#get_why
Authorrepowise-dev
Version1.0.0
Installs0
System Documentation
What problem does it solve?
This skill helps engineering teams understand the rationale behind architectural decisions in a Repowise-indexed codebase. It surfaces and organizes why certain design choices were made, by aggregating decision markers from code comments (WHY:, DECISION:, TRADEOFF:, ADR:), commit history, and documentation, so teams can reason about changes and maintain consistency.
Core Features & Use Cases
- Surface existing decisions for a given area using get_why to surface rationale from code, commits, and docs.
- Review and audit architectural decisions before making changes to ensure alignment with prior reasoning.
- Monitor decision health and hotspots with a dashboard-like view to identify ungoverned areas.
- Record new decisions by adding standardized markers or using dedicated tooling (e.g., repowise decision add).
Quick Start
Call get_why(query="the area you're changing") to surface existing decisions relevant to that area.
Dependency Matrix
Required Modules
None requiredComponents
Standard package💻 Claude Code Installation
Recommended: Let Claude install automatically. Simply copy and paste the text below to Claude Code.
Please help me install this Skill: Name: architectural-decisions Download link: https://github.com/repowise-dev/repowise/archive/main.zip#architectural-decisions Please download this .zip file, extract it, and install it in the .claude/skills/ directory.
Agent Skills Search Helper
Install a tiny helper to your Agent, search and equip skill from 471,000+ vetted skills library on demand.