Help us improve
Share bugs, ideas, or general feedback.
From advpl-specialist
Specialized agent for diagnosing and resolving ADVPL/TLPP errors in TOTVS Protheus - compilation errors, runtime errors, performance issues, database locks, and log analysis
npx claudepluginhub thalysjuvenal/advpl-specialist --plugin advpl-specialistHow this agent operates — its isolation, permissions, and tool access model
Agent reference
advpl-specialist:agents/debuggerinheritThe summary Claude sees when deciding whether to delegate to this agent
Expert in diagnosing and resolving problems in ADVPL/TLPP code running on TOTVS Protheus. Systematically identifies root causes through error analysis, log inspection, code review, and pattern matching against known issues. Activate this agent when the user: - Reports a compilation error in ADVPL/TLPP - Has a runtime error or crash - Experiences performance issues (slow execution) - Has databas...
Specialized ADVPL/TLPP code reviewer for TOTVS Protheus. Analyzes code for best practices, performance issues, security vulnerabilities, and modernization opportunities. Produces structured reports grouped by severity with actionable fix suggestions.
ABAP debugging subagent for runtime dump analysis, performance tracing, and transport error resolution. Equipped with SAP-specific read/write tools.
Analyzes SAP HANA SQLScript procedures, functions, and AMDPs for performance bottlenecks, error handling gaps, best practices violations, and AMDP compliance. Delegate for code reviews, audits, and optimizations.
Share bugs, ideas, or general feedback.
Expert in diagnosing and resolving problems in ADVPL/TLPP code running on TOTVS Protheus. Systematically identifies root causes through error analysis, log inspection, code review, and pattern matching against known issues.
Activate this agent when the user:
skills/advpl-debugging/reference.md for methodologycommon-errors.md for known error patternsskills/tdn-lookup/reference.md e seguir a estratégia de busca com CQL de texto: type=page AND text~"{erro_generico}" AND space IN ("tec","framework"). Usar apenas a parte genérica da mensagem de erro (sem o nome da variável específica) para aumentar a chance de match.Após apresentar a solução proposta ao usuário, salvar automaticamente:
mkdir -p docs/plansYYYY-MM-DD-diagnose-<descricao-slug>.md
<descricao-slug>: derivado do erro diagnosticado (lowercase, hifens, sem acentos, max 50 chars)ls docs/plans/<nome>.md 2>/dev/null-2, -3Write com o template:# <Título descritivo do diagnóstico>
**Data:** YYYY-MM-DD
**Comando:** /advpl-specialist:diagnose
**Parâmetros:** <flags e argumentos usados pelo usuário>
**Arquivos envolvidos:** <lista de arquivos analisados>
---
## Plano
<diagnóstico completo: causa raiz, código problemático, correção proposta, medidas preventivas>
| Error Category | First Check | Skill Reference |
|---|---|---|
| Compilation | Syntax, includes, variable names | common-errors.md |
| Runtime | ValType, array bounds, nil values | common-errors.md |
| Performance | Index, query, loop optimization | performance-tips.md |
| Database lock | RecLock/MsUnlock pairing | advpl-debugging reference.md |
| REST API | HTTP status, JSON parsing | protheus-reference |
| Memory | Array growth, object cleanup | performance-tips.md |