cc-version-analysis

Analyze CC CLI version upgrade impacts on bkit plugins and components.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a repeatable, multi-phase workflow to detect and evaluate the impact of Claude Code (CC) CLI version upgrades on the bkit ecosystem, removing guesswork and ensuring tracked, auditable findings.

Core Features & Use Cases

  • Structured Research: Automated collection of changelogs, GitHub releases, issues, PRs, npm metadata, and official docs to build a comprehensive change report.
  • Impact Analysis & Mapping: Maps CC changes to bkit components (agents, skills, hooks, libs, scripts), assesses test coverage and philosophical compliance, and identifies prioritized ENH items.
  • Report & Task Integration: Generates templated Korean reports, updates MEMORY.md and project docs, and creates tracked tasks for each phase to ensure PDCA continuity.
  • Use Case: When a new CC release appears, run the skill to produce a Korean impact report, an ENH roadmap, and task-tracked artifacts for engineering planning.

Quick Start

Analyze CC CLI upgrade from the installed version to the specified target version and produce a structured Korean impact report with prioritized ENH items.

Frequently Asked Questions about cc-version-analysis

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

FAQPage Schema
How do I assess the impact of a Claude Code CLI version upgrade on my plugins?

Assess Claude Code CLI upgrade impact by researching GitHub releases, issues, PRs, npm registry, and official docs to identify breaking changes and map compatibility risks to your plugins and repository components.

What's the best way to map breaking changes from CLI updates to specific agents and scripts?

Map breaking changes by analyzing collected changelog data and mapping identified modifications to your specific agents, skills, hooks, libs, and scripts to assess test coverage and philosophical compliance.

Can I generate a structured release research report from GitHub issues and npm registry data?

Generate a structured release research report by aggregating data from GitHub releases, issues, PRs, npm metadata, and official docs to produce a comprehensive change report with a prioritized ENH roadmap.

Does this version analysis workflow support creating task-tracking artifacts for engineering planning?

The version analysis workflow supports engineering planning by creating task-tracking artifacts for each phase to ensure PDCA continuity, updating project documentation and MEMORY.md with the findings.

When do I need to run a CLI version compatibility risk assessment for my repository components?

Run a CLI version compatibility risk assessment when a new Claude Code release appears to evaluate its impact, produce an impact report, and generate a prioritized ENH roadmap for your repository components.