Trace downstream impact chains of SX3 fields across ADVPL sources and Protheus dictionaries.
npx skills add https://github.com/JoniPraia/plugadvpl --skill plugadvpl-impacto
Please help me install this Agent Skill. Skill: /plugadvpl:impacto Source: https://github.com/JoniPraia/plugadvpl/tree/main/skills/impacto Command: npx skills add https://github.com/JoniPraia/plugadvpl --skill plugadvpl-impacto
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.
.prw/.tlpp references.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.tipo, local, contexto, and severidade so you can quickly prioritize where to investigate.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.
High-intent search queries and answers about installing and using this skill.
Tracing the impact of an SX3 field change in Protheus requires identifying all dependent validations, triggers, and questions. This analysis computes downstream matches with boundary rules per row type and outputs structured rows with context and severity.
An SX3 field impact analysis includes all `.prw` and `.tlpp` source references, SX3 validation rules like X3_VALID and X3_VLDUSER, SX7 trigger wiring, and SX1 questions referencing the field to provide a complete chain-of-impact view.
Yes, you must run the ingest-sx process to build a local index before analyzing Protheus SX3 dependencies. The impact analysis requires this existing local index to compute matches and output structured rows with severity.
To find affected SX7 triggers and SX1 questions after an ADVPL field edit, run an impact analysis. It lists all SX7 triggers where the field appears as origin or destination and SX1 questions referencing it via X1_VALID or X1_DEF01..X1_DEF99.
You can assess the blast radius of a Protheus dictionary change by computing the complete downstream impact chain across ADVPL sources and dictionaries. The analysis outputs structured rows with tipo, local, contexto, and severidade for quick triage.
Your ADVPL field impact analysis assumes UTF-8 encoding only because it follows an encoding-safe workflow guidance. This approach supports the index flow where you must run ingest before analysis to ensure accurate static indexing.
TheOrcDevReplace array.includes() membership checks with native Set/Map lookups.
Ryno-Crypto-Mining-ServicesTrace errors back to their original trigger using stack traces and instrumentation.
jeremylongshoreGenerate ERD diagrams and data dictionaries from existing database schemas.
daymadeCorrect ASR transcription errors using dictionary rules, GLM AI, and SQLite learning.