vibe-boundary-check
CommunityKeep code complexity and size within limits.
Software Engineering#governance#complexity#code-quality#static-analysis#dead-code#loc#boundary-check
Authorjacobcy
Version1.0.0
Installs0
System Documentation
What problem does it solve?
Detects when repository code metrics exceed governance budgets by measuring total LOC, per-file size, per-function size, functions-per-file, and identifying dead code so teams can prevent bloat and over-design.
Core Features & Use Cases
- Governance-driven checks: Loads budgets and enforcement lists from .agent/governance.yaml and evaluates core directories against those thresholds.
- Metric reporting: Produces a structured summary of total LOC, largest files, longest functions, function counts per file, and a list of suspected dead code.
- Use Case: Run during local development saves and CI/pre-merge checks to generate compliance evidence for PRs and guide maintainers on targets for refactoring or pruning.
Quick Start
Run a boundary check across the repository to generate a markdown compliance report listing LOC, largest files, longest functions, functions-per-file, and detected dead code.
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: vibe-boundary-check Download link: https://github.com/jacobcy/vibe-coding-control-center/archive/main.zip#vibe-boundary-check 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.