Cc Version AnalysisSAFE
bkit Vibecoding Kit - PDCA methodology + Claude Code mastery for AI-native development
Overview
bkit Vibecoding Kit - PDCA methodology + Claude Code mastery for AI-native development
f9b6b0c367f8OBSERVED · 2026-10-14Host compatibility
What the documentation claims. We have not run a compatibility test.
| Host | Status | Notes |
|---|---|---|
| claude-code | mentioned |
What it tells the agent
The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.
---
name: cc-version-analysis
classification: workflow
classification-reason: 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
argument-hint: "[from_version] [to_version]"
user-invocable: true
agents:
research: bkit:cc-version-researcher
analyze: bkit:bkit-impact-analyst
report: bkit:report-generator
allowed-tools:
- Read
- Write
- Edit
- Glob
- Grep
- Bash
- Task
- TaskCreate
- TaskUpdate
- TaskList
- TaskGet
- AskUserQuestion
- Agent
- WebSearch
- WebFetch
imports:
- ${PLUGIN_ROOT}/templates/cc-version-analysis.template.md
- ${PLUGIN_ROOT}/templates/plan-plus.template.md
- ${PLUGIN_ROOT}/templates/report.template.md
next-skill: pdca plan
pdca-phase: null
task-template: "[CC-Version-Analysis] CC v{from} → v{to}"
---
# CC Version Analysis — Claude Code CLI 버전 영향 분석 워크플로우
> CC CLI 버전 업그레이드 시 bkit plugin에 대한 영향을 체계적으로 조사, 분석하고
> 개선 기회를 도출하는 전문 워크플로우 스킬.
## Overview
이 스킬은 CC CLI의 새 버전이 출시되었을 때 다음을 자동화합니다:
1. **Phase 1 (Research)**: CC 변경사항 심층 조사
2. **Phase 2 (Analyze)**: bkit 아키텍처 영향 분석
3. **Phase 3 (Brainstorm)**: Plan Plus 브레인스토밍으로 개선안 도출
4. **Phase 4 (Report)**: 종합 영향 분석 보고서 작성
**Agent Team 구성**:
- `cc-version-researcher`: CC 버전 변경사항 외부 조사
- `bkit-impact-analyst`: bkit 내부 아키텍처 영향 분석
- `report-generator`: 최종 보고서 생성
## HARD-GATE
<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.
</HARD-GATE>
## 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
```
## Process Flow
```
┌─────────────────────────────────────────────────────┐
│ CC Version Analysis │
├─────────────────────────────────────────────────────┤
│ │
│ Phase 0: Setup & Version Detection │
│ ├── Detect installed CC version (claude --version) │
│ ├── Determine target version (args or latest) │
│ ├── Create Task tracking structure │
│ └── Load previous analysis from memory │
│ │
│ Phase 1: Research (cc-version-researcher agent) │
│ ├── Official docs (code.claude.com) │
│ ├── GitHub (anthropics/claude-code) │
│ │ ├── Releases & changelog │
│ │ ├── Issues (open & recently closed) │
│ │ ├── PRs (merged in version range) │
│ │ └── Commits (significant changes) │
│ ├── npm registry (@anthropic-ai/claude-code) │
│ ├── Technical blogs & community │
│ └── Output: CC Change Report (structured) │
│ │
│ Phase 1.5: Raw Source Verification Gate (MANDATORY) │
│ ├── WebFetch https://github.com/anthropics/ │
│ │ claude-code/releases/tag/v{to} │
│ ├── WebFetch https://raw.githubusercontent.com/ │
│ │ anthropics/claude-code/main/CHANGELOG.md │
│ ├── Cross-check agent's bullet count vs raw count │
│ ├── If mismatch → raw wins, record errata │
│ ├── Spot-check ≥3 random Fixed bullets verbatim │
│ └── Block Phase 2 if any mismatch unresolved │
│ │
│ Phase 2: Analyze (bkit-impact-analyst agent) │
│ ├── Map CC changes → bkit components │
│ ├── Identify ENH opportunities │
│ ├── File impact matrix │
│ ├── Philosophy compliance check │
│ ├── Test impact assessment │
│ └── Output: bkit Impact Analysis (structured) │
│ │
│ Phase 3: Brainstorm (Plan Plus methodology) │
│ ├── Intent discovery (핵심 목표/리스크/기회) │
│ ├── Alternative exploration │
│ ├── YAGNI review (각 ENH 필요성 검증) │
│ ├── Priority assignment (P0~P3) │
│ └── Output: Prioritized ENH roadmap │
│ │
│ Phase 4: Report Generation │
│ ├── Merge all phase outputs │
│ ├── Generate from template │
│ │ (cc-version-analysis.template.md) │
│ ├── Save to docs/04-report/features/ │
│ ├── Update MEMORY.md (version history) │
│ └── Output: Final Impact Report (Korean) │
│ │
└─────────────────────────────────────────────────────┘
```
## Phase Details
### Phase 0: Setup & Version Detection
```
1. Detect installed CC version:
$ claude --version
2. Determine target version:
- If args provided: use specified versions
- If noTrust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | NA |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- none-observed
- Shell
- none-observed
- Dependencies
- pinned
- Secrets in source
- none-found
Findings (0)
No findings outside the package's declared scope.
Gates applied: no_behavioural_pass.
f9b6b0c367f8full audit observations/trust-audit/skill/popup-studio-ai__cc-version-analysis.json · Report an issue / request a re-scanAudit history
Every audit this skill has had.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-14 | f9b6b0c367f8 | SAFE | B | 89 | first audit |
Questions
What does the Cc Version Analysis skill do?
bkit Vibecoding Kit - PDCA methodology + Claude Code mastery for AI-native development
Is Cc Version Analysis safe to install?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean skill reads B.
What can Cc Version Analysis access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
Which assistants does Cc Version Analysis work with?
Its documentation mentions claude-code. That is what the text claims, not a compatibility test we ran.
How current is this page?
The grade is for one exact copy of the source (f9b6b0c367f8), read on 2026-10-14. The repository is watched, and a new audit runs when it changes — this is the first audit.