plugadvpl-index-usage

Retrieve structured ADVPL metadata from a local SQLite index.

Updated Aug 27, 2026

Search Tags:#token optimization #lint #call graph #code indexing #advpl #protheus #sqlite fts5

Ready to run

npx skills add https://github.com/JoniPraia/plugadvpl --skill plugadvpl-index-usage

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plugadvpl-index-usage
Source: https://github.com/JoniPraia/plugadvpl/tree/main/skills/plugadvpl-index-usage
Command: npx skills add https://github.com/JoniPraia/plugadvpl --skill plugadvpl-index-usage

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents wasting Claude context by stopping you from reading entire ADVPL sources (.prw/.prx/.tlpp/.apw) when indexed metadata can answer the question precisely.

Core Features & Use Cases

Mandatory index-first workflow: forces index lookups before any raw Read of ADVPL files, reducing tokens by 10–50×.
Targeted commands by question type: supports architecture lookup, function discovery, callers/callees, table impact, MV_* parameter tracing, SX7 trigger chains, grep-style project search, and lint findings.
Edit-safe guardrails for cp1252 .prw: enforces a required stage/commit workflow to avoid accent corruption when writing .prw files.

Quick Start

Ask an AI: “Where is the function FATA050 and who calls it?” and use the index-first commands to find it before reading any .prw content.

Frequently Asked Questions about plugadvpl-index-usage

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

FAQPage Schema

How do I find ADVPL function callers and callees in a Protheus codebase without reading entire source files?▼

Trace MV_ parameter usage by querying the plugadvpl SQLite index to retrieve structured ADVPL metadata, letting you locate parameter references across a Protheus codebase without opening whole source files.

What is the best way to trace MV_ parameter usage and SX7 trigger chains across Protheus code?▼

Trace MV_ parameter usage and SX7 trigger chains by querying the local plugadvpl SQLite index, which retrieves structured ADVPL metadata to answer cross-reference questions without opening whole source files.

Can I search ADVPL table usage for SA1 and SC5 tables using an indexed metadata approach?▼

Yes, you can search ADVPL table usage for SA1 and SC5 by querying the local plugadvpl SQLite index. It retrieves structured metadata to answer table impact questions without opening whole source files.

How do I perform a lint-oriented investigation or grep-style project search on ADVPL source code?▼

Perform lint-oriented investigations and grep-style project searches on ADVPL code by querying the plugadvpl SQLite index, which supports output shaping via format, limit, and offset flags to retrieve targeted metadata.

Why does editing cp1252 encoded .prw files in Protheus risk accent corruption and how can I avoid it?▼

Editing cp1252 .prw files risks accent corruption because standard text editors may not preserve the encoding. The plugadvpl index enforces a required stage and commit workflow to ensure edit-safe guardrails when writing .prw files.