skills.rest
rachel353
rachel353COMMUNITY
Explore all skills by this author →
GitHub

change-analyzer

Classify frontend change requests into Added, Removed, Modified, or Impact-shift with impact scope.

Updated Apr 7, 2026
Search Tags:#documentation#frontend#analyze#change-management#impact-analysis#tasks.json
One-click install
npx skills add https://github.com/rachel353/fullty-plan --skill change-analyzer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: change-analyzer
Source: https://github.com/rachel353/fullty-plan/tree/main/.claude/skills/change-analyzer
Command: npx skills add https://github.com/rachel353/fullty-plan --skill change-analyzer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzes FE change requests and breaks them down into clear change types and their impact scope to deliver actionable planning data.

Core Features & Use Cases

  • Atomic decomposition of change requests into Added, Removed, Modified, and Impact-shift
  • Impact analysis across screens, components, state, and styling
  • Generates metadata and triggers change-doc workflow for documentation alignment

Quick Start

Provide the raw change request to the analyzer to begin structured breakdown.

Frequently Asked Questions about change-analyzer

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

FAQPage Schema
How do I analyze frontend change requests for impact scope?▼

To analyze frontend change requests, decompose them into Added, Removed, Modified, or Impact-shift categories and map the impact across screens, components, state, and styling to produce actionable planning data.

What is the best way to structure FE change feedback for tasks.json?▼

Structuring FE change feedback for tasks.json involves classifying changes into specific types and generating a machine-readable change log with metadata and references while preserving the original feedback for traceability.

How does impact analysis work for frontend design reviews?▼

Impact analysis for frontend design reviews works by atomically breaking down change requests and outlining their specific effects on UI screens, component states, and styles to prepare data for documentation workflows.

Can I use this to trigger a change-doc workflow for policy updates?▼

Yes, you can use this for policy updates by classifying the changes and generating structured change items with metadata, which automatically triggers the change-doc workflow for documentation alignment.

Do I need to format raw change requests before analyzing impact scope?▼

No, you do not need to pre-format raw change requests; you can provide the raw change request directly to the analyzer to begin the structured breakdown and impact assessment.

Why does classifying changes as Impact-shift matter for component state?▼

Classifying changes as Impact-shift matters because it identifies modifications that alter existing component state or styling behaviors without adding or removing features, ensuring accurate documentation alignment.

Related Skills

Explore More Software Engineering Skills→
rachel353rachel353

change-doc

Reconcile FE design documents and tasks.json from change-analyzer outputs and feedback.

Community
Advanced
joannanowakowskajoannanowakowska

openspec-propose

Generate OpenSpec change proposals with design and task artifacts.

Community
Advanced
daithang59daithang59
1

Add React Component

Scaffold React components with styling, context, API integration, and tests.

Community
Advanced
sapdev-aisapdev-ai
7

sap-explain-object

Explain ABAP objects by generating a read-only dossier with structure and call graph.

Official
Advanced