メニュー
Find overly complex code: files over 300 lines, functions over 50 lines, deeply nested conditions (4+ levels), and magic numbers. Use for code quality reviews, pre-release checks, or when asked to assess code maintainability.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/davila7/claude-with-skills --skill complexity-checkコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Explains code in plain language for someone unfamiliar with the programming language. Use when asked to explain code, walk through logic, describe what a function does, or when the user says "explain this" or "walk me through this".
Summarizes uncommitted git changes in a concise machine-readable format. Use in CI pipelines, scripts, or headless invocations where the output will be piped or captured.
Explains what a skill is and demonstrates that skills are working. Use when testing skills, when asked about skills, or when asked to demonstrate how skills work.
SOC 職業分類に基づく
SKILL.md を表示中
| title | complexity-check |
| name | complexity-check |
| description | Find overly complex code: files over 300 lines, functions over 50 lines, deeply nested conditions (4+ levels), and magic numbers. Use for code quality reviews, pre-release checks, or when asked to assess code maintainability. |
| context | fork |
| agent | Explore |
| allowed-tools | Grep Glob Read Bash(find *) Bash(wc *) |
Check the codebase for complexity violations.
!git diff --name-only HEAD~1 2>/dev/null || git diff --name-only origin/main...HEAD 2>/dev/null || echo "all"
Focus on the changed files listed above. If "all", check the entire codebase.
Find source files over 300 lines (exclude node_modules, dist, .git, vendor, coverage, build):
find . \( -name "*.py" -o -name "*.ts" -o -name "*.js" -o -name "*.tsx" -o -name "*.jsx" -o -name "*.go" -o -name "*.rb" \) \
-not -path "*/node_modules/*" \
-not -path "*/dist/*" \
-not -path "*/.git/*" \
-not -path "*/vendor/*" \
-not -path "*/coverage/*" \
-not -path "*/build/*" \
| xargs wc -l 2>/dev/null | sort -rn | head -20
Flag any file with more than 300 lines.
Read each changed source file (or sample the largest files if "all"). Scan for function or method definitions and estimate the line count between consecutive definitions. Flag any function that appears to span more than 50 lines.
Look for these definition patterns:
def or async def function , async function , => {, ): void {, ): Promise<func def If a definition is followed by the next definition more than 50 lines later, flag the first function.
Search changed files for lines with 4 or more levels of indentation inside conditional or loop structures. Use these grep patterns (adjust for tab vs space indentation):
For 4-space indentation (16+ spaces):
grep -n "^ " <file>
For tab indentation (4+ tabs):
grep -n "^\t\t\t\t" <file>
Flag files where deeply nested lines appear inside if, for, while, or switch blocks.
Search changed files for numeric literals (other than 0, 1, -1, 2, 100, 1000) used directly in conditions or calculations without a named constant. Look for patterns like:
if x > 42:* 3600% 7 ==timeout = 30Exclude test files and configuration files where literal values are expected.
Output exactly:
COMPLEXITY FINDINGS:
- <file>:<line> — <description>
Examples:
COMPLEXITY FINDINGS:
- src/auth/handler.ts:1 — file is 412 lines (limit: 300)
- src/auth/handler.ts:87 — function processLogin is approximately 63 lines (limit: 50)
- src/utils/parser.py:145 — 5 levels of nesting detected
- src/config.ts:23 — magic number 86400 (consider: SECONDS_PER_DAY)
If no findings: output exactly COMPLEXITY FINDINGS: none
Do not add any prose before or after the findings block.