/plugadvpl:impacto

What problem does it solve?

When a specific ADVPL field (from SX3) changes or breaks behavior, it’s hard to know which validations, triggers, and questions across your Protheus codebase are impacted. This Skill identifies every downstream usage chain so you can assess impact without manually hunting through thousands of lines.

Core Features & Use Cases

• SX3 impact graph: Finds all sources that mention an SX3 field, including .prw/.tlpp references.
• Validation + UI dependencies: Detects SX3 rules that depend on the field (X3_VALID, X3_WHEN, X3_VLDUSER, X3_RELACAO).
• Trigger and question reachability: Lists SX7 triggers where the field appears as origin/destination and SX1 questions referencing it (X1_VALID, X1_DEF01..X1_DEF99), enabling a complete chain-of-impact view.
• Encoding-safe workflow guidance: Assumes UTF-8-only Claude read/edit behavior and supports the index flow where you must run ingest before analysis.
• Use Case: If you need to understand how changing A1_COD affects customer-related behavior, you can discover every .prw usage plus related SX3 validations, SX7 trigger wiring, and SX1 questions that reference it.
• Practical output for triage: Produces rows with tipo, local, contexto, and severidade so you can quickly prioritize where to investigate.

Quick Start

Run impacto for the field you’re investigating (for example, A1_COD) after ingesting SX metadata so you get the full chain of impacted sources, validations, triggers, and questions.