skills.rest
doccker
docckerCOMMUNITY
Explore all skills by this author →
GitHub

cc-size-check

Review changed code for reuse and quality, then scan project files for line-count limit violations.

1.0k|109|Updated Jan 4, 2026
Search Tags:#line count#Refactoring#css extraction#file size#code simplification#Code review#Code quality
One-click install
npx skills add https://github.com/doccker/cc-use-exp --skill cc-size-check
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cc-size-check
Source: https://github.com/doccker/cc-use-exp/tree/main/.codex/skills/cc-size-check
Command: npx skills add https://github.com/doccker/cc-use-exp --skill cc-size-check

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Codebases accumulate oversized files, duplicated logic, and bloated inline styles that make maintenance painful. This Skill reviews changed code for reuse, quality, and efficiency issues, scans the whole project for files exceeding per-language line limits, and proposes concrete split or simplification plans before fixing them with your confirmation.

Core Features & Use Cases

  • Code Simplification Review: Detects duplicated code, over-abstraction, redundant logic, and dead code in changed files, then fixes the issues found.
  • File Size Scanning: Scans the project (excluding node_modules, dist, build, and similar directories) against per-language thresholds such as 300 lines for Java/TypeScript/Python, 400 for Go, and 200 for Vue/TSX/JSX, producing a violation report with split suggestions.
  • CSS Extraction Checks: Flags Vue/TSX/JSX files whose inline <style> blocks exceed 30 lines or use non-scoped global styles, recommending extraction to assets/styles/.
  • Use Case: After a large feature branch, run a full-project scan to get a table of oversized files with split recommendations, confirm the fixes, and let the Skill split files while preserving original exports and running the project test suite.

Quick Start

Ask the AI to run a size check across the whole project and list every file exceeding its line-count threshold with split suggestions.

Frequently Asked Questions about cc-size-check

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

FAQPage Schema
How do I check which files in my project exceed line-count limits?▼

Run a full-project scan without specifying a file. The Skill counts lines in every code file, compares them against per-language thresholds (300 for Java/TypeScript/Python, 400 for Go, 200 for Vue/TSX/JSX), and outputs a violation table with split suggestions.

How to simplify duplicated or over-abstracted code automatically?▼

The code simplification review checks changed code for duplicated logic, unnecessary design patterns, redundant branches, and unused imports or dead code. It then fixes the issues found, extracting shared methods or components where repetition exists.

What line-count limits apply to Vue, Go, and Python files?▼

Vue and TSX/JSX files are limited to 200 lines, Go files to 400 lines, and Java, TypeScript, JavaScript, and Python files to 300 lines. Files exceeding these thresholds receive concrete split recommendations such as extracting composables, helpers, or subcomponents.

Does the file size scan include node_modules or build output?▼

No. The scan excludes node_modules, vendor, dist, build, .git, __pycache__, and .venv directories, plus minified files, lock files, and config formats like JSON, YAML, and TOML. Markdown files skip line limits but are checked for duplicate sections.

When should inline CSS be extracted from Vue components?▼

Extraction is recommended when a <style> block exceeds 30 lines or when a Vue SFC uses a non-scoped global <style> block. Scoped styles of 30 lines or fewer are left untouched, and extracted styles move to assets/styles/.

Will splitting oversized files break existing functionality?▼

The Skill requires user confirmation before any fix, keeps original exports and interfaces intact in entry files, and runs the project's test suite after changes. If no tests exist, it outputs a change list for manual verification.

Related Skills

Explore More Software Engineering Skills→
VYRE-StudiosVYRE-Studios

commit

Guide git commit creation with diff review and conventional message formatting.

Official
Intermediate
Srajangpt1Srajangpt1

dev6-review-fix

Apply code review fixes, run tests, and create a git commit.

Community
Intermediate
GGEduGGEdu

springboot-verification

Automate end-to-end verification of Spring Boot services with builds, tests, and security scans.

Community
Advanced
archibatearchibate
6

code-quality-metrics

Measure code complexity and quality metrics across multi-language repositories.

Community
Intermediate