skills.rest
JoniPraia
JoniPraiaCOMMUNITY
Explore all skills by this author →
GitHub

/plugadvpl:trace

Trace cross-universe references and workflow dependencies for ADVPL/TLPP entities.

Updated Aug 27, 2026
Search Tags:#workflow#impact analysis#trace#sqlite fts5#protheus advpl#sx metadata#execauto
One-click install
npx skills add https://github.com/JoniPraia/plugadvpl --skill plugadvpl-trace
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: /plugadvpl:trace
Source: https://github.com/JoniPraia/plugadvpl/tree/main/skills/trace
Command: npx skills add https://github.com/JoniPraia/plugadvpl --skill plugadvpl-trace

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of figuring out what breaks (or what is affected) when you change a Protheus ADVPL/TLPP entity like a field, function, or table, without having to run multiple separate analysis commands and correlate their outputs manually.

Core Features & Use Cases

  • Unified cross-universe impact trace across sources, SX metadata, and workflow/execauto/docs in one aggregated result.
  • Automatic entity type detection (field, function, table, file, parameter, or pergunta) with an override when the heuristic is ambiguous.
  • Graph depth exploration with controllable BFS depth and per-edge hit limits to reduce noise and explosion.
  • Use cases: diagnose regressions from a field change, identify who writes to a table, and determine whether a function is unused or only triggered indirectly.

Quick Start

Run /plugadvpl:trace A1_COD to get a unified trace of every reference and workflow impact related to the field A1_COD.

Frequently Asked Questions about /plugadvpl:trace

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

FAQPage Schema
How do I trace the impact of changing a Protheus ADVPL field or function?▼

You can trace the impact of an ADVPL entity by running a unified cross-universe analysis that aggregates all source references, SX metadata, and workflow dependencies to show exactly what is affected by your change.

What is cross-universe impact analysis in Protheus ADVPL?▼

Cross-universe impact analysis in Protheus ADVPL is the process of tracking all references and relationships across sources, SX metadata, and workflow/execauto/docs for a specific entity to explain what it touches and who depends on it.

How do I find out who writes to a specific Protheus table or if a function is unused?▼

To find out who writes to a Protheus table or if a function is unused, you perform a unified trace with controllable BFS depth to identify all direct and indirect dependencies, writers, and triggers across the codebase.

Does the ADVPL trace support automatic detection for different entity types like parameters and pergunte groups?▼

Yes, the ADVPL trace supports automatic entity type detection for fields, functions, tables, source files, parameters (MV_), and SX1 pergunte groups, including an override option when the heuristic is ambiguous.

Can I limit the depth of graph exploration to reduce noise during an ADVPL impact trace?▼

Yes, you can limit graph exploration depth during an ADVPL impact trace by controlling the BFS depth and applying max-per-edge hit limits to reduce noise and prevent relationship explosion.

Related Skills

Explore More Software Engineering Skills→
lis186lis186
46

pattern-finder

Search a repository for code patterns and return matching files with line numbers.

Community
Basic
astronomerastronomer
419

tracing-downstream-lineage

Trace downstream data lineage and assess impact across tables, DAGs, and dashboards.

Official
Intermediate
babdulhakim2babdulhakim2

Phone Number Lookup

Analyze phone numbers to identify carrier, line type, and risk indicators.

Community
Basic
thalysjuvenalthalysjuvenal
176

protheus-reference

Provide ADVPL/TLPP function syntax, data dictionary tables, REST API endpoints, and MV_* parameters.

Community
Intermediate