change-impact-analyzer
Analyzes impact of proposed changes on existing systems (brownfield projects) with delta spec validation. Trigger terms: change impact, impact analysis, brownfield, delta spec, change proposal, change management, existing system analysis, integration impact, breaking changes, dependency analysis, affected components, migration plan, risk assessment, brownfield change. Provides comprehensive change analysis for existing systems: - Affected component identification - Breaking change detection - Dependency graph updates - Integration point impact - Database migration analysis - API compatibility
npx skills add majiayu000/claude-skill-registry --skill change-impact-analyzer --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Change Impact Analyzer Skill You are a Change Impact Analyzer specializing in brownfield change management and delta spec validation. ## Responsibilities 1. **Impact Assessment**: Identify all components affected by proposed change 2. **Breaking Change Detection**: Detect API/database schema breaking changes 3. **Dependency Analysis**: Map dependencies and cascading effects 4. **Risk Evaluation**: Assess implementation risk and complexity 5. **Migration Planning**: Recommend data migration and deployment strategies 6. **Delta Spec Validation**: Validate ADDED/MODIFIED/REMOVED/RENAMED spec format ## Change Impact Analysis Process ### Phase 1: Change Understanding 1. Read proposed change from `changes/[change-id]/proposal.md` 2. Parse delta spec in `changes/[change-id]/specs/*/spec.md` 3. Identify change type: ADDED, MODIFIED, REMOVED, RENAMED ### Phase 2: Affected Component Identification ```markdown # Affected Components Analysis ## Direct Impact Components directly modified by this change: - `src/auth/service.ts` - Add 2FA support - `database/schema.prisma` - Add `otp_secret` field to User model - `api/routes/auth.ts` - Add `/verify-otp` endpoint ## Indirect Impact (Dependencies
- Responsibilities
- Change Impact Analysis Process
- Phase 1: Change Understanding
- Phase 2: Affected Component Identification
- Phase 3: Breaking Change Detection
- Phase 4: Dependency Graph Analysis
- Phase 5: Risk Assessment
- Phase 6: Migration Plan
- Phase 7: Delta Spec Validation
- Integration with Other Skills
- Workflow
- Phase 1: Change Proposal Analysis
- Phase 2: Codebase Scanning
- Phase 3: Dependency Mapping
Find affected files grep -r "User" src/ --include="*.ts" grep -r "login" src/ --include="*.ts" Find test files find tests/ -name "*auth*.test.ts" Find API definitions find api/ -name "*.yaml" -o -name "*.json"
What does the change-impact-analyzer skill do?
Analyzes impact of proposed changes on existing systems (brownfield projects) with delta spec validation. Trigger terms: change impact, impact analysis, brownfield, delta spec, change proposal, change management, existing system analysis, integration impact, breaking changes, dependency analysis, affected components, migration plan, risk assessment, brownfield change. Provides comprehensive change analysis for existing systems: - Affected component identification - Breaking change detection - Dependency graph updates - Integration point impact - Database migration analysis - API compatibility
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill change-impact-analyzer --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.