field-rename-verification
CommunityFully trace renamed fields across services
Software Engineering#verification#api-contract#data-model#dependency-analysis#field-rename#service-boundary
Authorbordenet
Version1.0.0
Installs0
System Documentation
What problem does it solve?
Renaming a field or changing an API contract often leaves hidden dependencies unchecked, leading to runtime failures across services.
Core Features & Use Cases
- Comprehensive Traceability: Guides users to search all repositories, map READ/STORE/PASS paths, and verify type definitions.
- Cross‑Service Verification: Provides checklists for service boundaries, integration testing, and configuration updates.
- Failure Prevention: Highlights common missed patterns and offers a gate function to ensure complete verification before declaring a rename finished.
Quick Start
Ask the assistant to run a full field‑rename verification for the field “trackingLine” before merging the change.
Dependency Matrix
Required Modules
None requiredComponents
Standard package💻 Claude Code Installation
Recommended: Let Claude install automatically. Simply copy and paste the text below to Claude Code.
Please help me install this Skill: Name: field-rename-verification Download link: https://github.com/bordenet/superpowers-plus/archive/main.zip#field-rename-verification Please download this .zip file, extract it, and install it in the .claude/skills/ directory.
Agent Skills Search Helper
Install a tiny helper to your Agent, search and equip skill from 471,000+ vetted skills library on demand.