CC CLI version upgrade impact analysis — research changes, analyze bkit impact, generate report.
Triggers: cc-version-analysis, CC upgrade, version analysis
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.
Orchestrates multi-phase research and analysis pipeline independent of model capability
deprecation-risk
none
effort
high
description
CC CLI version upgrade impact analysis — research changes, analyze bkit impact, generate report.
Triggers: cc-version-analysis, CC upgrade, version analysis
CC Version Analysis — Claude Code CLI 버전 영향 분석 워크플로우
CC CLI 버전 업그레이드 시 bkit plugin에 대한 영향을 체계적으로 조사, 분석하고
개선 기회를 도출하는 전문 워크플로우 스킬.
Overview
이 스킬은 CC CLI의 새 버전이 출시되었을 때 다음을 자동화합니다:
Phase 1 (Research): CC 변경사항 심층 조사
Phase 2 (Analyze): bkit 아키텍처 영향 분석
Phase 3 (Brainstorm): Plan Plus 브레인스토밍으로 개선안 도출
Phase 4 (Report): 종합 영향 분석 보고서 작성
Agent Team 구성:
cc-version-researcher: CC 버전 변경사항 외부 조사
bkit-impact-analyst: bkit 내부 아키텍처 영향 분석
report-generator: 최종 보고서 생성
HARD-GATE
Do NOT skip any phase. Each phase produces artifacts that feed into the next.
Do NOT generate the final report without completing Research and Analysis phases.
Do NOT implement any ENH items — this skill is analysis-only.
All documents MUST be written in Korean (한국어).
NEW (v2.1.16 errata learning — added 2026-05-20):
Do NOT advance from Phase 1 → Phase 2 without completing the Phase 1.5
Raw Source Verification Gate. The cc-version-researcher agent's quantitative
claims (bullet count, issue counts, file counts) MUST be cross-checked against
≥2 raw sources (GitHub release tag URL + raw CHANGELOG.md URL) before being
adopted into the report. The v2.1.145 cycle leaked an unverified bullet count
of 21 (actual: 20) and an unverified agent count of 36 (actual: 34) because
this gate did not exist. If raw and agent disagree, raw wins.
Invocation
/cc-version-analysis # Auto-detect: installed vs latest
/cc-version-analysis 2.1.78 2.1.85 # Specific version range
/cc-version-analysis to 2.1.85 # From current installed to target
1. Detect installed CC version:
$ claude --version
2. Determine target version:
- If args provided: use specified versions
- If no args: search for latest available version
3. Create Task structure:
TaskCreate: "[CC-Version-Analysis] CC v{from} → v{to}"
├── Task: "Phase 1: CC 변경사항 조사"
├── Task: "Phase 2: bkit 영향 분석"
├── Task: "Phase 3: Plan Plus 브레인스토밍"
└── Task: "Phase 4: 보고서 작성"
4. Load previous analysis context:
- Read memory/cc_version_history_*.md
- Read last ENH number from MEMORY.md
- Read existing PDCA status from .bkit/state/pdca-status.json
Phase 1: Research (Agent: cc-version-researcher)
Input: from_version, to_version
Output: Structured CC Change Report
Launch the cc-version-researcher agent with:
Research CC CLI changes from v{from} to v{to}.
Sources: official docs, GitHub (issues/PRs/releases), npm, blogs.
Categorize by: Breaking/Feature/Fix/Performance/SystemPrompt/Hook/Config.
Rate impact: HIGH/MEDIUM/LOW.
Flag bkit-relevant changes.
Output structured markdown tables.
Parallel research tasks (when using Agent Team):
Task 1: GitHub releases + changelog
Task 2: GitHub issues (open + recently closed)
Task 3: Official docs changes
Task 4: System prompt diff analysis
Phase 1.5: Raw Source Verification Gate (MANDATORY — added 2026-05-20)
Why: cc-version-researcher's output may paraphrase, summarize, or miscount.
The v2.1.145 cycle revealed that a single WebFetch (via the model-processed
release tag page) under-counted by 1 bullet (reported 6 Added, actual 7).
A second fetch against raw CHANGELOG.md is required to catch this.
prompt: "Show the FULL v{to_version} section verbatim. List every bullet
exactly as written, in order, under the original headings (Added/Fixed/
Improved/Breaking/etc). Do NOT summarize."
Compare to cc-version-researcher's reported counts:
If raw and agent disagree → raw wins. Record discrepancy in report
under §3.0 "Verification Notes" with both numbers.
Spot-check ≥3 random Fixed bullets — verify verbatim text in agent report
matches raw.
Block Phase 2 progression if any mismatch is unresolved.
Output: §3.0 Verification table appended to Phase 1 output:
Field
Agent reported
Raw verified
Source URL
Verdict
Added
N
M
raw CHANGELOG
match / errata
Fixed
N
M
raw CHANGELOG
match / errata
Improved
N
M
raw CHANGELOG
match / errata
Breaking
N
M
raw CHANGELOG
match / errata
Total bullets
N
M
sum
match / errata
Phase 2: Analyze (Agent: bkit-impact-analyst)
Input: Phase 1 CC Change Report PLUS Phase 1.5 verification tableOutput: bkit Impact Analysis
Pre-flight check before launching the analyst agent: the analyst will
measure bkit architecture stats (agents/skills/hooks counts) via Bash. If
the analyst proposes a numeric correction to memory (e.g. "agents 34 → 36"),
the main session MUST re-run the measurement command independently before
accepting it. See "Numeric Correction Protocol" in bkit-impact-analyst.md.
Launch the bkit-impact-analyst agent with:
Analyze bkit impact from these CC changes: {phase1_output}
Map each change to bkit components (agents/skills/hooks/lib/scripts).
Identify ENH opportunities starting from ENH-{last+1}.
Check philosophy compliance (Automation First, No Guessing, Docs=Code).
Assess test impact per ENH.
All work MUST be tracked via Task Management System:
[CC-Version-Analysis] CC v{from} → v{to} # Parent task
├── [Research] Phase 1: CC 변경사항 조사 # cc-version-researcher
│ ├── GitHub releases 조사
│ ├── GitHub issues 조사
│ ├── 공식 문서 변경 조사
│ └── 시스템 프롬프트 변경 분석
├── [Analyze] Phase 2: bkit 영향 분석 # bkit-impact-analyst
│ ├── 컴포넌트 매핑
│ ├── ENH 기회 식별
│ ├── 파일 영향 매트릭스
│ └── 철학 준수 검증
├── [Brainstorm] Phase 3: 브레인스토밍 # Plan Plus
│ ├── 의도 탐색
│ ├── 대안 탐색
│ └── YAGNI 검토
└── [Report] Phase 4: 보고서 작성 # report-generator
├── 템플릿 기반 보고서 생성
├── MEMORY.md 업데이트
└── 최종 검토
Agent Team Configuration
When invoked with CTO Team (/pdca team):
Role
Agent
Model
Task
Lead
cto-lead
fable
Overall orchestration
Researcher
cc-version-researcher
opus
Phase 1: CC research
Analyst
bkit-impact-analyst
opus
Phase 2: bkit analysis
Reporter
report-generator
haiku
Phase 4: Report writing
Parallel execution:
Phase 1 tasks can run in parallel (GitHub, docs, npm)
Phase 2 depends on Phase 1 completion
Phase 3 depends on Phase 2 completion
Phase 4 depends on Phase 3 completion
Quality Checklist
Before completing, verify:
All CC changes from version range are captured
Every change has impact classification (HIGH/MEDIUM/LOW)
Every ENH has priority (P0/P1/P2/P3)
Philosophy compliance checked for all ENH items
File impact matrix is complete
Test impact assessed for all ENH items
Report is written in Korean
MEMORY.md is updated
Task tracking shows all items completed
Executive Summary includes 4-perspective value table
Raw Verification Checklist (NEW — Phase 1.5 gate, v2.1.16 errata learning)
Raw GitHub release tag URL fetched (releases/tag/v{to})
Raw CHANGELOG.md URL fetched (raw.githubusercontent.com)
Bullet counts cross-verified (agent vs raw, both numbers reported)
≥3 spot-check bullets confirmed verbatim against raw
Numeric corrections re-verified via direct Bash measurement before adoption
§3.0 Verification table included in report (5 rows: Added/Fixed/Improved/Breaking/Total)
Errata entries recorded in memory file under "Known Errata" section if any mismatches occurred
Known Errata Log (errata learning archive)
When raw verification catches a discrepancy with agent output, record it here
to prevent repeat-mistakes and to feed future skill improvements.
Cycle v2.1.145 (2026-05-20)
Field
Agent reported
Raw verified
Root cause
Bullet count
21 (Features 7 + Fixes 13 + Improved 1)
20 (Added 7 + Fixed 12 + Improved 1)
Agent over-counted Fixed by 1; first WebFetch on model-processed release page under-reported Added by 1 (raw CHANGELOG was authoritative)
Agents directory count
36 (proposed correction from 34)
34 (ls -1 agents/ | wc -l)
Analyst proposed unverified numeric correction; main session adopted without re-measurement
F7-145 background_tasks/session_crons
"extension surface" (no clear source citation)
Confirmed in raw CHANGELOG Added #7 verbatim
Single-source WebFetch had originally omitted this bullet; second raw fetch recovered it
Lessons applied to skill (this commit):
Phase 1.5 Raw Verification Gate now mandatory before Phase 2
