cc-version-analysis

Automate CC CLI version upgrade impact analysis for the bkit plugin.

2|1|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/solitasroh/mcukit --skill cc-version-analysis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cc-version-analysis
Source: https://github.com/solitasroh/mcukit/tree/main/skills/cc-version-analysis
Command: npx skills add https://github.com/solitasroh/mcukit --skill cc-version-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill orchestrates a structured, multi-phase CC CLI version upgrade impact analysis workflow within Claude Code, enabling comprehensive research, analysis, brainstorming, and reporting to manage upgrade risk and opportunities.

Core Features & Use Cases

  • End-to-end upgrade impact analysis: automates phase-based investigation of CC CLI changes and their effects on the bkit plugin.
  • Artifact-driven workflow: produces phase outputs (change reports, impact analysis, ENH roadmap, final report) and updates memory/history.
  • Team-based coordination: maps responsibilities to agents (researcher, analyst, reporter) and supports parallel execution.

Quick Start

Run /cc-version-analysis to auto-detect versions and drive the four-phase PDCA workflow from research to final report.

Frequently Asked Questions about cc-version-analysis

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

FAQPage Schema
How do I analyze Claude Code CLI version upgrade impact on my plugin?

To analyze Claude Code CLI version upgrade impact, this Skill automates a four-phase PDCA workflow covering research, analysis, brainstorming, and reporting to identify changes and map effects to your plugin components.

What is a structured workflow for managing CC upgrade risk?

A structured CC upgrade risk workflow orchestrates multi-phase investigation, producing artifact-driven outputs like change reports and impact analysis while mapping responsibilities to agents for parallel execution.

How do I map CC CLI changes to bkit components during an upgrade?

Mapping CC CLI changes to bkit components happens during the analysis phase, which evaluates new version changes and generates an ENH roadmap to manage upgrade opportunities and risks.

Can I automate Claude Code version research and reporting across multiple phases?

Yes, you can automate Claude Code version research and reporting by running a phase-based workflow that auto-detects versions and drives investigation from initial research through to final report generation.

Do I need to manually track version artifacts when analyzing CC CLI upgrades?

No, you do not need to manually track version artifacts when analyzing CC CLI upgrades because the workflow enforces automatic memory updates and generates phase-based artifacts including change reports and history.