How does this skill measure context health?

It calculates a score (0-100) based on modules per context, public API surface size, dependency fan-in/fan-out, and the presence of circular dependencies or boundary violations.

Does it require any external Elixir dependencies?

No, it primarily utilizes the built-in 'mix xref' tool and standard Elixir project structures to perform its dependency and boundary analysis.

Can it automatically fix architectural issues?

Yes, using the --fix flag, the skill analyzes the violations and suggests specific code changes to move logic to the correct architectural layer or resolve illegal dependencies.

What are the 'Iron Laws' it enforces?

The Iron Laws ensure controllers only call contexts, schemas remain pure data without side effects (no Repo calls), and cross-context dependencies remain explicit and intentional.

When should I use the --assess mode?

Use --assess when you want a high-level overview of your project's technical debt or when you need to justify architectural refactoring to stakeholders with quantified data.

Phoenix Context Boundary Validator

Name: Phoenix Context Boundary Validator
Author: oliver-kriska

byoliver-kriska

•

API 개발

Validates architectural integrity and dependency boundaries in Elixir Phoenix applications using automated analysis.

This skill empowers developers to maintain clean software architecture within Elixir Phoenix projects by enforcing strict context boundaries. It leverages mix xref to detect circular dependencies, illegal cross-context calls, and 'Iron Law' violations—such as controllers accessing the database directly. Whether you are performing a code review, planning a major refactor, or assessing the overall health of your application's modularity, this tool provides quantitative scoring and actionable fixes to prevent technical debt and ensure long-term maintainability.

주요 기능

01Visualized dependency graph analysis and API surface area measurement

02Automated context health scoring (0-100) based on modularity metrics

03Suggested refactoring plans for splitting large contexts and fixing violations

04Enforcement of 'Iron Laws' including no Repo access in controllers or schemas

05Detection of circular dependencies and illegal cross-context calls

0662 GitHub stars

사용 사례

01Automating architectural reviews during the Pull Request process

02Auditing a legacy Phoenix codebase before starting a major refactor

03Planning the decomposition of bloated contexts into manageable sub-contexts

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add oliver-kriska/claude-elixir-phoenix boundaries

For use in Claude.ai and ChatGPT

Download Skill