side-effect

Analyze code changes for consumer, shared state, UI, and signature impacts.

3|3|Updated Aug 19, 2025
One-click install
npx skills add https://github.com/StartaleGroup/app-sdk --skill side-effect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: side-effect
Source: https://github.com/StartaleGroup/app-sdk/tree/main/.claude-lib/shared/skills/side-effect
Command: npx skills add https://github.com/StartaleGroup/app-sdk --skill side-effect

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

After code changes, this skill helps identify and prevent unintended regressions by analyzing how changes ripple through consumers, shared state, UI components, function signatures, and layout.

Core Features & Use Cases

  • Consumer impact analysis: trace who imports or uses changed modules and verify compatibility.
  • Shared state & data layer checks: assess Zustand stores, TanStack Query caches, context providers, and storage keys for regressions.
  • UI components & layout checks: evaluate affected components for CSS selectors, layout cascades, and behavior changes.
  • API & signature validation: ensure function signatures remain compatible and import paths are updated.

Quick Start

Run a change-diff analysis on the current workspace and execute the Explore agent across all changed files to assess consumer, state, UI, and signature impacts.

Frequently Asked Questions about side-effect

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

FAQPage Schema
How do I detect unintended side effects after a code change?

Identify unintended side effects by running a change-diff analysis across changed files to evaluate consumer impact, shared state dependencies, UI behavior, and function signatures.

What is the best way to check for UI regressions when refactoring components?

Check for UI regressions by evaluating affected components for CSS selectors, layout cascades, and behavior changes to ensure refactors do not alter visual output.

How do I trace consumer impact for modified function signatures?

Trace consumer impact by analyzing who imports or uses changed modules, verifying that function signatures remain compatible and import paths are updated.

Does this side-effect analysis work with Zustand stores and TanStack Query caches?

Yes, side-effect analysis works with Zustand stores and TanStack Query caches by assessing shared state, context providers, and storage keys for potential data layer regressions.

Why does updating a shared state module cause layout cascades in unrelated components?

Updating shared state can cause layout cascades because changes ripple through context providers and UI components, altering CSS selectors and layout interactions in dependent files.