change-analysis

Analyze code changes to assess functional impact and test coverage.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/taptap/agents-plugins --skill change-analysis
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: change-analysis
Source: https://github.com/taptap/agents-plugins/tree/main/plugins/test/skills/change-analysis
Command: npx skills add https://github.com/taptap/agents-plugins --skill change-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates systematic analysis of code changes to determine functional impact, cross-module risks, and test coverage gaps so teams can make informed release and testing decisions.

Core Features & Use Cases

  • Incremental code-change analysis: ingest MR/PR links or local diffs, classify change points, and produce a detailed code_change_analysis.md with per-change findings and confidence levels.
  • Impact and coverage assessment: evaluate functional and cross-service impact, enforce Android external-interaction checks, generate change_analysis.json and structured coverage reports, and produce supplementary test cases for uncovered risks.
  • Integration and outputs: fetch related requirement documents, run platform-specific rules (e.g., Android AIDL/scheme checks), and output change_coverage_report.json, test_coverage_report.md, and optional supplementary_cases.json for CI or QA workflows.
  • Use case: Given a Story with linked PRs, run a full Story scenario to produce an impact summary, prioritized action items, and P0/P1 test cases for QA.

Quick Start

Analyze the provided MR/PR link and diffs, then output change_analysis.json and a test coverage report with suggested supplementary test cases.

Frequently Asked Questions about change-analysis

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

FAQPage Schema
How do I analyze code changes to assess test coverage and functional impact?▼

Code change impact analysis evaluates functional and cross-service risks by parsing MR/PR diffs, performing callgraph analysis, and enforcing Android external-interaction checks to generate structured coverage reports and supplementary test cases.

What is the best way to generate supplementary test cases from a diff analysis?▼

Supplementary test case generation from diff analysis evaluates uncovered risks by parsing code changes and outputting supplementary_cases.json, providing P0/P1 test cases for QA workflows to cover cross-module impact.

Can I use MR PR links to perform code change impact analysis on multi-repo Android codebases?▼

Yes, code change impact analysis supports multi-repo and Android service codebases by ingesting MR/PR links, enforcing Android AIDL and scheme external-interaction checks, and producing structured change_analysis.json artifacts.

Does code change impact analysis work with Story and Bug scenarios across multi-repo codebases?▼

Yes, code change impact analysis applies to Story and Bug scenarios across multi-repo codebases by fetching related requirement documents, running platform-specific Android rules, and producing impact summaries with prioritized action items.

How do I enforce Android external-interaction checks during code change analysis?▼

Android external-interaction checks are enforced during code change analysis by applying platform-specific rules, including AIDL and scheme checks, when parsing diffs and evaluating cross-service impact across Android codebases.

What limitations exist when performing diff analysis on local code changes without related requirement docs?▼

Without related requirement docs, diff analysis on local code changes loses requirement context, limiting the ability to produce comprehensive impact summaries and prioritized P0/P1 test cases for full Story or Bug scenarios.