architectural-decisions-9592d4 — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited architectural-decisions-9592d4 (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Repowise captures architectural decisions: the rationale behind how code is built.
Call get_why(query="specific area or decision") to search captured decisions. This covers inline decision markers, git-derived rationale, and decisions mined from documentation.
get_why(query="the area being changed") before introducing new patterns, restructuring modules, replacing infrastructure, or choosing between approaches.Call get_why() to inspect decision health: stale decisions, conflicts, and ungoverned hotspots.
If a file contains WHY:, DECISION:, TRADEOFF:, or ADR:, call get_context(targets=["path/to/file"]) to retrieve the full file context and related decisions.
When the user makes a new architectural decision, suggest recording it with a DECISION: comment in the relevant code or with repowise decision add.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.