field-rename-verification

Verify renamed fields and API contracts across service boundaries.

8|1|Updated Jan 24, 2026

Search Tags:#verification #api-contract #data-model #dependency-analysis #field-rename #service-boundary

Ready to run

npx skills add https://github.com/bordenet/superpowers-plus --skill field-rename-verification

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: field-rename-verification
Source: https://github.com/bordenet/superpowers-plus/tree/main/skills/engineering/field-rename-verification
Command: npx skills add https://github.com/bordenet/superpowers-plus --skill field-rename-verification

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about field-rename-verification

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

FAQPage Schema

How do I verify a field rename across multiple services?▼

Verify a field rename across multiple services by exhaustively grepping repositories, mapping READ, STORE, and PASS paths, checking type definitions, and testing cross-service integration flows to ensure no hidden dependencies remain unchecked.

What is API contract verification for data model refactors?▼

API contract verification for data model refactors is the process of tracing updated API shapes across service boundaries to ensure exhaustive path analysis and integration testing prevent runtime failures.

How do I trace hidden dependencies when changing an API shape?▼

Trace hidden dependencies when changing an API shape by performing exhaustive repository searches and mapping service boundaries to verify all READ, STORE, and PASS paths before merging the change.

What's the best way to test cross-service flows after updating an API contract?▼

The best way to test cross-service flows after updating an API contract is to map service boundaries, verify type definitions, and run integration tests to comprehensively check all paths and configuration updates.

When do I need exhaustive repository grep for field rename verification?▼

You need exhaustive repository grep for field rename verification when a data model refactor spans service boundaries and requires tracing all READ, STORE, and PASS paths to prevent hidden dependency failures.