deep-insight

Files (1)

• SKILL.md

SKILL.md (first lines)

## Inputs (skill args)

| 인자 | 의미 |
|---|---|
| (없음) | Auto-detect scope: 활성 세션의 changed files, 없으면 현재 디렉터리 |
| `<target>` | File path / directory / glob pattern |

빈 args / 매칭되지 않는 토큰 → 본문의 default 분기로 진입.

## Prerequisites


> **Quality Gate** — `/deep-test`가 Insight Tier로 자동 실행합니다 (차단 없음). 특정 대상의 메트릭/복잡도/의존성 분석이 필요할 때 직접 사용하세요.
> Standalone: `/deep-insight [target]`

# Code Insight Analysis

You are performing a **Code Insight Analysis** — measuring code metrics, complexity indicators, and dependency patterns to provide informational reports. This is the **Insight tier** of the 3-tier Quality Gate system.

## Critical Constraints

- **DO NOT modify any code files.** This is an analysis-only operation.
- **Read, analyze, and report findings.**
- **Insight results NEVER block the workflow.** They are purely informational.
- **Save analysis results to file when in workflow mode.**

## Instructions

### 1. Determine operating mode

Read(`${CLAUDE_PLUGIN_ROOT}/skills/deep-resume/references/session-detection.md`) and apply only its **Reusable session-state resolution** section to resolve `$STATE_FILE`; retain this skill's own no-session and standalone-mode behavior.

Check if `$STATE_FILE` exists and has an active session (`current_phase` is not `idle` and not empty).

**Workflow Mode** (active deep-work session):
- Read `work_dir` from the state file
- Set `WORK_DIR` to the value of `work_dir`
- Read `$WORK_DIR/plan.md` to extract the list of files (from "Files to Modify" section)
- Cross-reference with actual changes: `git diff --name-only` from baseline
- If `$WORK_DIR/file-changes.log` exists, use it for additional file tracking data
- Analysis scope: files listed in plan.md that were actually modified

**Standalone Mode** (no active session):
- If `$ARGUMENTS` is provided: use as target (file path, directory, or glob pattern)
- If `$ARGUMENTS` is empty: detect scope automatically:
  1. Check `git diff --name-only HEAD~1` for recently changed files
  2. If not a git repo or no changes, use current directory
- Analysis scope: all code files in detected scope (exclude node_modules, .git, __pycache__, build, dist, .next, vendor, etc.)

### 2. Collect analysis targets

Gather the list of files to analyze. For each file:
- Skip files that are clearly not code (README.md, .json config, .env, .lock, etc.)
- Skip files smaller than 3 lines (trivial)
- Skip auto-generated files (migrations, lock files, bundled output, .min.js)

If the total number of files exceeds 50, prioritize:
1. Files with the most lines of code
2. Files modified most recently
3. Files explicitly listed in plan.md (workflow mode)

Display progress:
```
ℹ️ Insight 분석 대상: [N]개 파일
  - src/auth/service.ts (245 lines)
  - src/models/user.ts (180 lines)
  - ...
```

If exceeding 50 files:
```
⚠️ 분석 대상이 50개를 초과합니다. 상위 50개 파일만 분석합니다.
```

### 3. Run built-in analyses

Execute 4 categories of analysis. Each analysis should be resilient — if one fails, continue with the rest.

#### 3A. File Metrics

For each target file, measure:
- **Lines of code** (excluding blank lines and comment-only lines)
- **Function/method count**: Use `grep -c` patterns appropriate for the language:
  - JS/TS: `function `, `=> {`, method definitions in classes
  - Python: `def `
  - Go: `func `
  - Rust: `fn `
  - Java/Kotlin: method patterns
  - Other: best-effort grep
- **Export count** (JS/TS: `export `, Python: `__all__`, Go: uppercase functions)

Generate summary table:

```markdown
## A. 파일 메트릭

| 파일 | 코드 줄 수 | 함수 수 | Export 수 |
|------|-----------|---------|----------|
| src/auth.ts | 245 | 12 | 5 |
| src/db.ts | 180 | 8 | 3 |

**합계**: 코드 425줄, 함수 20개, Export 8개
```

#### 3B. Complexity Indicators

For each target file, check:
- **Long files**: files exceeding 300 lines → flag with line count
- **Long functions**: functions exceeding 50 lines → identify function name and line range
  - Use heuristic: find function declarations, then count lines until matching closing brace/dedent
- **Deep nesting**: maximum indentation depth (count leading spaces/tabs)
  - Threshold: > 4 levels of nesting

Generate findings:

```markdown
## B. 복잡도 지표

### 대형 파일 (300줄 초과)

From Sungmin-Cho/deep-work, MIT.

More from Sungmin-Cho/deep-work