Analyze codebase architectural friction using Ousterhout's deep-module principle and generate RFC action files.
npx skills add https://github.com/psenger/ai-agent-skills --skill arch-lens
Please help me install this Agent Skill. Skill: arch-lens Source: https://github.com/psenger/ai-agent-skills/tree/main/skills/arch-lens Command: npx skills add https://github.com/psenger/ai-agent-skills --skill arch-lens
Explores codebase friction through Ousterhout's deep-module principle, enabling teams to identify shallow interfaces, hidden coupling, and testability seams for targeted RFC-driven improvements.
Follow the seven-step arch-lens workflow by loading WORKFLOW.md, DETECTION-PATTERNS.md, INTERFACE-DESIGN.md and executing Steps 1–7.
High-intent search queries and answers about installing and using this skill.
You can surface architectural friction by applying Ousterhout's deep-module principle to explore an entire repository or specific scope, which identifies shallow interfaces, hidden coupling, and testability seams for targeted improvements.
Translating architectural findings into an RFC involves a seven-step workflow that moves from exploration through candidate framing to RFC creation, generating dated RFC action files and structured design documentation for issue trackers.
Ousterhout's deep-module principle applies to architecture reviews by evaluating module interfaces against their underlying implementation complexity. It helps surface shallow modules that lack abstraction, highlighting areas needing design improvements through targeted RFCs.
Yes, architectural reviews can be scoped to user-specified boundaries instead of exploring an entire repository. This allows teams to target specific modules, surface localized hidden coupling, and generate focused RFC action files for those areas.
An RFC action file generated from an architectural review contains structured guidance for design, testing strategy, and documentation. It tracks identified friction signals, dependency categories, and testing impacts to drive safe architectural changes in issue trackers.
A structured workflow for codebase architecture refactoring should be used when you need to safely navigate hidden coupling and testability seams. It provides a seven-step process that frames issues and produces RFCs to guide secure design changes.
rajivpantVerify non-trivial code changes with seven adversarial integrity passes.
jonnymuirStandardize design documentation, execution tasks, and architectural decisions across multi-specialist projects.
bartolomeomuellerIdentify architectural friction and rank shallow module deepening opportunities.
ProgrammerAnthonyAnalyze code repositories to identify shallow modules, tight coupling, and testing barriers.
