/plugadvpl:workflow
CommunityFinds non-direct execution triggers in ADvPL
AuthorJoniPraia
Version1.0.0
Installs0
System Documentation
What problem does it solve?
It helps you determine whether an ADVPL/TLPP routine is executed indirectly via TOTVS workflow, schedule, AppServer standalone jobs, or automatic email sending, so you can analyze impact without manually reading huge .prw files.
Core Features & Use Cases
- Indexed execution trigger discovery: Detects
workflow,schedule,job_standalone, andmail_sendpatterns from source code. - Targeted filtering for impact analysis: Filter by trigger kind, target name (callback/Main/pergunte/variant), or source file basename to answer precise questions.
- Actionable output for next steps: Returns exact location (file, function, line, snippet) and rich per-kind metadata (e.g., process_id/to/subject/return callbacks, SX1-based schedule info, daemon loop parameters, email attachment usage).
- Cross-feature workflows: Supports follow-ups with
callers,arch, andlintto connect triggers to functionality and detect related risks.
Quick Start
Ask the AI to list all non-direct execution triggers in your project by running the workflow command with no filters.
Dependency Matrix
Required Modules
None requiredComponents
Standard package💻 Claude Code Installation
Recommended: Let Claude install automatically. Simply copy and paste the text below to Claude Code.
Please help me install this Skill: Name: /plugadvpl:workflow Download link: https://github.com/JoniPraia/plugadvpl/archive/main.zip#plugadvpl-workflow Please download this .zip file, extract it, and install it in the .claude/skills/ directory.
Agent Skills Search Helper
Install a tiny helper to your Agent, search and equip skill from 471,000+ vetted skills library on demand.