skills.rest
jacobcy
jacobcyCOMMUNITY
Explore all skills by this author →
GitHub

vibe-boundary-check

Detect codebase violations of size, complexity, and dead-code budgets.

6|Updated Feb 5, 2026
Search Tags:#governance#complexity#code-quality#static-analysis#dead-code#loc#boundary-check
One-click install
npx skills add https://github.com/jacobcy/vibe-coding-control-center --skill vibe-boundary-check
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: vibe-boundary-check
Source: https://github.com/jacobcy/vibe-coding-control-center/tree/main/supervisor/vibe-boundary-check
Command: npx skills add https://github.com/jacobcy/vibe-coding-control-center --skill vibe-boundary-check

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about vibe-boundary-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check code complexity and file size limits in a CI pipeline?▼

To check code complexity and file size limits in a CI pipeline, scan core repository directories against governance thresholds defined in a YAML configuration file. This generates a structured markdown compliance report highlighting violations for PR reviews.

What is dead code detection and how does it prevent codebase bloat?▼

Dead code detection identifies unused code segments to prevent codebase bloat and over-design. By measuring total lines of code and flagging dead code, teams can target refactoring and pruning efforts to maintain repository health.

How do I enforce a maximum functions-per-file limit during local development?▼

Enforce a maximum functions-per-file limit during local development by applying static analysis checks to local saves. The system evaluates files against budgets loaded from a governance configuration to flag violations.

Can I use a governance YAML file to set per-function size budgets?▼

Yes, you can use a governance YAML file to set per-function size budgets. The boundary check loads thresholds and enforcement lists from the configuration to evaluate core directories and produce compliance evidence.

What is the best way to generate PR compliance evidence for code quality?▼

The best way to generate PR compliance evidence for code quality is to run static analysis during pre-merge checks. This produces a structured markdown report summarizing LOC, largest files, and dead code to guide maintainers.

Related Skills

Explore More Software Engineering Skills→
artofrawrartofrawr
1

base

Enforce coding constraints and TDD workflow with atomic todos.

Community
Advanced
MODAC-AgentMODAC-Agent

gosu-review-v1

Generate Korean Markdown code-review reports from changed Go files.

Official
Advanced
liauw-medialiauw-media
3

pre-commit-hooks

Configure pre-commit hooks for JavaScript/TypeScript, Python, and PHP projects.

Community
Advanced
Chang-Shih-YungChang-Shih-Yung

health

Aggregate type checker, linter, and test results into a 0-10 composite score.

Community
Advanced