/plugadvpl:status

Check plugadvpl SQLite index health and freshness for ADVPL/TLPP code.

Updated Aug 27, 2026

Search Tags:#sqlite #code intelligence #call graph #version mismatch #stale files #index status #lint findings

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you verify whether your local plugadvpl SQLite index is present, up to date, and aligned with what the current runtime expects, avoiding wasted time on stale or mismatched indexing results.

Core Features & Use Cases

Index inventory: Reports total indexed source files, chunks/functions, and call graph calls.
Lint visibility: Shows how many lint findings are stored in the index.
Divergence detection: Compares runtime version vs the index version and warns when they differ, and optionally lists stale files via --check-stale.
Use Case: Before asking a Claude workflow questions about ADVPL/TLPP code, confirm the database actually reflects the current codebase state and toolchain version.

Quick Start

Run /plugadvpl:status --check-stale to confirm the index is fresh and identify any source files that may need reindexing.

Frequently Asked Questions about /plugadvpl:status

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

FAQPage Schema

How do I check if my ADVPL SQLite index is stale before querying code intelligence data?▼

Run a status check with the `--check-stale` flag to compare source file hashes and mtimes against the SQLite index, identifying any ADVPL or TLPP files that require reindexing to avoid stale symbol data.

What does a plugadvpl index status check show about call graph and lint coverage?▼

The index status check reports total indexed source files, chunks, functions, call graph calls, and stored lint findings, giving you a complete inventory of your ADVPL/TLPP code intelligence coverage.

Why does my ADVPL code index return mismatched results after a toolchain update?▼

A version mismatch occurs when the current runtime version differs from the frozen version stored in the SQLite index, which the status check detects and warns about to prevent querying outdated symbol data.

Can I detect which specific source files need reindexing in my ADVPL project?▼

Yes, use the `--check-stale` option to list specific source files that have changed based on file hashes and modification times, showing exactly which entries are stale and need reindexing.

When do I need to validate my local SQLite index for ADVPL code analysis?▼

Validate the index before running any Claude workflow questions about ADVPL/TLPP code to confirm the database reflects the current codebase state and toolchain version, avoiding wasted time on stale or mismatched results.