Structured Code Review
FareedKhan-dev/claude-code-from-scratch
Gives the agent a five-step review routine that reads the full file first, labels each finding as bug, security, performance, style or suggestion, and ends with a summary.
Reviews AdvPL and TLPP source against SonarQube rules, ProtheusDOC requirements, security, performance and Protheus conventions, and reports findings by severity.
Install AdvPL and TLPP Code Review
$ npx skills add totvs/engpro-advpl-tlpp-skills --skill code-review -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install totvs/engpro-advpl-tlpp-skills code-review --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/totvs/engpro-advpl-tlpp-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/advpl-tlpp/code-review .claude/skills/code-review && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "code-review" agent skill from https://github.com/totvs/engpro-advpl-tlpp-skills/tree/main/skills/advpl-tlpp/code-review into .claude/skills/code-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-review", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/totvs/engpro-advpl-tlpp-skills/tree/main/skills/advpl-tlpp/code-reviewType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add totvs/engpro-advpl-tlpp-skills --skill code-review -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install totvs/engpro-advpl-tlpp-skills code-review --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/totvs/engpro-advpl-tlpp-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/advpl-tlpp/code-review .agents/skills/code-review && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "code-review" agent skill from https://github.com/totvs/engpro-advpl-tlpp-skills/tree/main/skills/advpl-tlpp/code-review into .agents/skills/code-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-review", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add totvs/engpro-advpl-tlpp-skills --skill code-review -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install totvs/engpro-advpl-tlpp-skills code-review --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/totvs/engpro-advpl-tlpp-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/advpl-tlpp/code-review .cursor/skills/code-review && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "code-review" agent skill from https://github.com/totvs/engpro-advpl-tlpp-skills/tree/main/skills/advpl-tlpp/code-review into .cursor/skills/code-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-review", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/totvs/engpro-advpl-tlpp-skills.git --path skills/advpl-tlpp/code-review--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add totvs/engpro-advpl-tlpp-skills --skill code-review -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install totvs/engpro-advpl-tlpp-skills code-review --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/totvs/engpro-advpl-tlpp-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/advpl-tlpp/code-review .gemini/skills/code-review && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "code-review" agent skill from https://github.com/totvs/engpro-advpl-tlpp-skills/tree/main/skills/advpl-tlpp/code-review into .gemini/skills/code-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-review", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install totvs/engpro-advpl-tlpp-skills code-reviewInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add totvs/engpro-advpl-tlpp-skills --skill code-review -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/totvs/engpro-advpl-tlpp-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/advpl-tlpp/code-review .github/skills/code-review && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "code-review" agent skill from https://github.com/totvs/engpro-advpl-tlpp-skills/tree/main/skills/advpl-tlpp/code-review into .github/skills/code-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-review", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add totvs/engpro-advpl-tlpp-skills --skill code-review -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install totvs/engpro-advpl-tlpp-skills code-review --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/totvs/engpro-advpl-tlpp-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/advpl-tlpp/code-review .opencode/skills/code-review && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "code-review" agent skill from https://github.com/totvs/engpro-advpl-tlpp-skills/tree/main/skills/advpl-tlpp/code-review into .opencode/skills/code-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-review", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
code-review- GitHub stars
- 141
- Token cost
- ~2.5k tokens
- SKILL.md length
- 832 words
- Files
- 4 (incl. references)
- Skills in repo
- 19
- Repo updated
- First seen
- Licence
- MIT
At a glance
Reviews AdvPL and TLPP source against SonarQube rules, ProtheusDOC requirements, security, performance and Protheus conventions, and reports findings by severity.
- Works in 12 steps: Understand the Code → Load Relevant References → Run Review Categories → …
- Reviewing new or modified .prw, .tlpp or .prx files before merge
- SKILL.md covers Overview, When to Use, Bundled Reference Files and Review Process, plus 7 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Source files with the .prw, .tlpp or .prx extension are reviewed against TOTVS engineering standards, SonarQube static-analysis rules, ProtheusDOC documentation requirements and clean-code principles. The output is a categorized report with severity levels, rule references and fix suggestions that include code examples.
Typical uses are checking new or changed files, a pre-commit quality gate for pull requests, auditing legacy code for SonarQube compliance, confirming that ProtheusDOC blocks are complete, checking security posture such as SQL injection, hardcoded credentials and access control, and judging readiness for Cloud and SmartERP environments.
The skill loads detail on demand. Separate reference files cover security patterns, code quality and performance patterns including legacy code and metadata access, and documentation and naming conventions including TLPP specifics, while a shared SonarQube rules reference sits one level up in the repository.
When your agent uses it
- Reviewing new or modified .prw, .tlpp or .prx files before merge
- Auditing legacy AdvPL code for SonarQube compliance
- Checking that ProtheusDOC blocks are complete and correct
- Looking for SQL injection or hardcoded credentials in Protheus code
Example prompts
- “Review src/FATA050.prw for security problems and missing ProtheusDOC blocks.”
- “Audit this TLPP class against the SonarQube rules and list findings by severity.”
- “Code review the changed .tlpp files in this pull request before I merge.”
Workflow steps
12 steps, taken from the step headings in SKILL.md.
- Understand the Code
- Load Relevant References
- Run Review Categories
- Produce the Report
- Security (SonarQube G1)
- Performance and Loops (SonarQube G2)
- Legacy and Deprecated Code (SonarQube G3)
- Metadata Access (SonarQube G4)
- ProtheusDOC Documentation
- Clean Code and Naming Conventions
- TLPP-Specific Checks
- Compilation and Encoding (SonarQube G5)
What it can do on your machine
Read from SKILL.md and the folder at commit 3908e4e. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
AdvPL and TLPP Code Review loads about 2.5k tokens when it runs, and up to ~6.8k if it reads all its reference files. Until then it costs about 90 tokens; SKILL.md has 832 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from totvs/engpro-advpl-tlpp-skills at commit 3908e4e, republished under its MIT licence (© totvs). 832 words, ~2,530 tokens.
Download SKILL.mdSave it as
.claude/skills/code-review/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- code-review
- description
- Perform comprehensive AdvPL/TLPP code review covering SonarQube rules, Protheus.doc documentation, security, performance, clean code, and TOTVS Protheus framework best practices. Use when a user says "review this code", "code review", "check this source", "audit this AdvPL/TLPP", or needs a structured quality assessment of .prw/.tlpp/.prx files.
- license
- MIT
- metadata.domain
- Protheus
- metadata.maintainer
- Customizações ADVPL/TLPP
- metadata.author
- Thalion Starforge
- metadata.version
- 4.2.0
- metadata.category
- Code Quality and Review
AdvPL/TLPP Code Review
You are an expert AdvPL/TLPP code reviewer. Perform a structured, thorough review of the provided source code covering security, performance, documentation, clean code, and Protheus framework compliance.
Overview
This skill reviews AdvPL and TLPP source files against TOTVS engineering standards, SonarQube static-analysis rules, ProtheusDOC documentation requirements, and clean-code principles. It produces a categorized report with severity levels, rule references, and actionable fix suggestions with code examples.
When to Use
- Reviewing new or modified
.prw,.tlpp, or.prxsource files - Pre-commit quality gate for pull request reviews
- Auditing legacy code for SonarQube compliance
- Checking that ProtheusDOC blocks are complete and correct
- Verifying security posture (SQL injection, hardcoded credentials, access control)
- Assessing code readiness for Cloud/SmartERP environments
Bundled Reference Files
This skill uses progressive disclosure. The SKILL.md body covers the review workflow, category definitions, checklist, and output format. Detailed code examples, anti-patterns, and rule-specific fixes are in the references/ directory — read them on demand based on the review scenario:
| Reference File | When to Read | Content |
|---|---|---|
| references/security-review-patterns.md | Reviewing security concerns — SQL injection, hardcoded credentials, restricted APIs, environment context | SQL injection examples, FWExecStatement patterns, restricted functions table, REST/SOAP environment rules |
| references/code-quality-patterns.md | Reviewing performance, legacy code, metadata access, or compilation issues | Loop/transaction anti-patterns, ISAM migration, deprecated API replacements, SX* metadata access table, encoding rules |
| references/documentation-and-conventions.md | Reviewing ProtheusDOC, naming conventions, clean code, or TLPP-specific patterns | ProtheusDOC tag reference, common documentation mistakes, variable naming/scope conventions, TLPP type annotations, namespace, Try-Catch |
Also refer to references/sonarqube-rules-reference.md for the complete SonarQube rules reference shared across skills.
Review Process
Step 1 — Understand the Code
Before reviewing:
- Read the entire file to understand purpose, scope, and dependencies
- Identify the element types (Functions, Static Functions, Classes, Methods)
- Note the file extension —
.prw(AdvPL),.tlpp(TLPP),.prx(legacy) - Check the includes —
totvs.ch,tlpp-core.th, custom.ch/.thfiles
Step 2 — Load Relevant References
Based on the code under review, read the appropriate reference files:
- Security findings → read references/security-review-patterns.md
- Performance / legacy / metadata findings → read references/code-quality-patterns.md
- Documentation / clean code / TLPP findings → read references/documentation-and-conventions.md
- Full review → read all three reference files
Step 3 — Run Review Categories
Apply each review category below in order. For every finding, record:
- Category (Security, Performance, Documentation, Clean Code, Framework)
- Severity (CRITICAL, MAJOR, MINOR, INFO)
- Rule ID (SonarQube rule when applicable, e.g., CA2050)
- Location (function/method name and approximate line)
- Finding (what is wrong)
- Fix (how to correct it, with code example when helpful)
Step 4 — Produce the Report
Output findings as a structured report grouped by category, ordered by severity (CRITICAL first). End with a summary and overall assessment.
Review Categories
1. Security (SonarQube G1)
Check for vulnerabilities that expose the application to attacks or data leaks. Key rules:
- CA2050 / CA2051 — SQL Injection: concatenating user input in SQL strings → use
FWExecStatement(CRITICAL) - CA2052 — Hardcoded credentials in source → use environment configuration (CRITICAL)
- BG1000 —
RpcSetEnv/RpcSetTypein REST/SOAP services → configurePrepareIn(MAJOR) - CA2022–CA2025, CA2053 — Restricted/prohibited functions and assignments (CRITICAL)
- BG1200 —
ErrorBlockoverride → migrate toTry-Catchin TLPP (INFO)
Show full SKILL.md (345 more words)Show less
2. Performance and Loops (SonarQube G2)
Detect patterns that degrade runtime performance:
- CA1003 — Prohibited APIs inside loops (
GetMV,SuperGetMV,ExistBlock,AllUsers,Type,Pergunte) → cache before loop (MAJOR) - CA1002 — UI APIs inside transactions (
MsgAlert,MsgYesNo, etc.) → move UI after transaction (MAJOR) - CS1000 — Direct SQL without evaluation → prefer framework APIs or
ChangeQuery()/BeginSQL(MAJOR)
3. Legacy and Deprecated Code (SonarQube G3)
Identify deprecated APIs and legacy patterns:
- CA1000 — ISAM driver access (
MSCREATE,DBCREATE) →FWTemporaryTable(MAJOR) - CA1001 — File-based semaphores →
LockByName()(MAJOR) - CA1004 — Console output (
ConOut) →FWLogMsg()(MINOR) - CA4000 —
IIFinline → explicitIf/Else/EndIf(INFO) - CA3001 — Uppercase
#INCLUDE→ lowercase#include(MINOR)
Obsolete Include Directives — Flag any of these legacy includes and recommend replacement:
| Obsolete Include | Replacement Include | Modern Class/API |
|---|---|---|
Ap5Mail.ch | totvs.ch | TMailMessage() |
ApWizard.ch | totvs.ch | FWWizardControl() |
FileIO.ch | totvs.ch | FWFileWriter() / FWFileReader() |
Font.ch | totvs.ch | TFont() |
ParmType.ch | totvs.ch | Default prefix for parameter handling |
protheus.ch | totvs.ch | — |
RWMake.ch | totvs.ch | — |
4. Metadata Access (SonarQube G4)
Direct DbSelectArea on Protheus system tables (SX*) is prohibited. All SX* tables (SM0, SIX, SX1–SXG, SXD, SE5, SPF) must be accessed through framework APIs. Key rules: CA2000–CA2013, CA2017–CA2019, CA2021 (CRITICAL/MAJOR).
5. ProtheusDOC Documentation
Every public element must have a complete /*/{Protheus.doc} block with mandatory tags: @type, @author, @since, @param (per parameter), @return. Static Functions should also be documented.
6. Clean Code and Naming Conventions
Check variable naming prefixes (c=Character, n=Numeric, l=Logical, etc.), Local vs Private scope, function size (< 50 lines), magic numbers, and dead code.
7. TLPP-Specific Checks
For .tlpp files: verify file extension consistency, type annotations on variables and functions, namespace usage, and Try-Catch error handling instead of ErrorBlock.
8. Compilation and Encoding (SonarQube G5)
Check syntax errors (CA0000), file encoding (Windows-1252), INI references (CA1005), and I18N compliance (CA2016).
Report Format
Output the review as follows:
# Code Review: <filename>
## Summary
- **Total Findings:** <count>
- **Critical:** <count> | **Major:** <count> | **Minor:** <count> | **Info:** <count>
- **Overall Assessment:** <PASS | PASS WITH OBSERVATIONS | NEEDS REVISION | FAIL>
## Critical Findings
### [CA####] <Title>
- **Location:** `FunctionName` (line ~NN)
- **Finding:** <description>
- **Fix:** <how to fix>
```advpl
// suggested fix code
```Major Findings
(same structure)
Minor Findings
(same structure)
Info / Recommendations
(same structure)
Documentation Review
- All public elements documented with ProtheusDOC
- @type, @author, @since present on all blocks
- @param tags match function signatures
- @return documented for non-void functions
- Identifiers match element names exactly
Assessment Criteria
| Category | Status | Notes |
|---|---|---|
| Security (G1) | ✅/⚠️/❌ | |
| Performance (G2) | ✅/⚠️/❌ | |
| Legacy/Deprecated (G3) | ✅/⚠️/❌ | |
| Metadata Access (G4) | ✅/⚠️/❌ | |
| Documentation | ✅/⚠️/❌ | |
| Clean Code | ✅/⚠️/❌ | |
| TLPP Compliance | ✅/⚠️/❌ | (if .tlpp file) |
| Compilation (G5) | ✅/⚠️/❌ |
### Overall Assessment Criteria
| Assessment | Condition |
|------------|-----------|
| **PASS** | Zero CRITICAL, zero MAJOR findings |
| **PASS WITH OBSERVATIONS** | Zero CRITICAL, ≤ 3 MAJOR findings |
| **NEEDS REVISION** | Zero CRITICAL, > 3 MAJOR findings |
| **FAIL** | Any CRITICAL finding |
---
## Quick Reference: All SonarQube Rules
For the complete rule definitions, severity levels, prohibited patterns, and required alternatives, consult [references/sonarqube-rules-reference.md](../references/sonarqube-rules-reference.md).
| Group | Rules | Focus |
|-------|-------|-------|
| G1 — Security | BG1000, CA2022–CA2053, BG1200 | Injection, credentials, restricted APIs |
| G2 — Performance | CA1002, CA1003, CS1000 | Loops, transactions, queries |
| G3 — Legacy | CA1000–CA1006, CA2014–CA2020, CA3001–CA3002, CA4000, BG1100 | Deprecated APIs, ISAM, console |
| G4 — Metadata | CA2000–CA2013, CA2021 | Direct SX* table access |
| G5 — Compilation | CA0000, CA1005, CA2016 | Syntax, encoding, I18N |
© totvs, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 3 other files (references) in skills/advpl-tlpp/code-review of totvs/engpro-advpl-tlpp-skills.
- SKILL.md
- references/code-quality-patterns.md
- references/documentation-and-conventions.md
- references/security-review-patterns.md
Open the folder on GitHubat commit 3908e4e
Compare with similar skills
AdvPL and TLPP Code Review next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| AdvPL and TLPP Code Review this skilltotvs/engpro-advpl-tlpp-skills | 141 | — | ~2.5k | Automated safety check: Pass | MIT | |
| Structured Code ReviewFareedKhan-dev/claude-code-from-scratch | 298 | — | ~809 | Automated safety check: Pass | MIT | |
| WooCommerce Code Reviewwoocommerce/woocommerce | 11k | 3 repos | ~1.1k | Automated safety check: Pass | Custom licence | |
| Skill Doli Code ReviewDolibarr/dolibarr | 7.7k | 1 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Dignified Python Standardsdocling-project/docling | 68k | — | ~1.5k | Automated safety check: Pass | Apache-2.0 | |
| Clean Code GuardamElnagdy/guard-skills | 1.3k | 2 repos | ~4.3k | Automated safety check: Pass | MIT |
Similar skills
WooCommerce Code Review
woocommerce/woocommerce
Reviews WooCommerce code changes against the project's standards, flagging backend PHP architecture, naming, documentation, data integrity and testing violations.
Skill Doli Code Review
Dolibarr/dolibarr
Reviews Dolibarr PHP code for compliance with coding standards and security best practices, and fixes identified issues.
Dignified Python Standards
docling-project/docling
Applies opinionated production Python conventions chosen by the project's Python version: modern type syntax, pathlib, explicit checks and interface guidance.
Clean Code Guard
amElnagdy/guard-skills
Reviews generated or changed production code against Clean Code, SOLID, DRY, KISS, YAGNI and LLM-specific failure modes before it ships, in any language.
Archify Review
tt-a1i/archify
Review Archify issues, PRs, or code through value, cost, and impact to support evidence-based maintenance decisions. Use for issue triage, change reviews, and…
More from totvs/engpro-advpl-tlpp-skills
All 19 skills in this repoAdvPL UTF-8 to CP1252 Converter
totvs/engpro-advpl-tlpp-skills
Converts AdvPL and TLPP source files from UTF-8 to Windows-1252 in place after code generation, because the Protheus compiler accepts only CP1252 files.
AdvPL/TLPP Compile in VS Code
totvs/engpro-advpl-tlpp-skills
Compiles AdvPL and TLPP sources from VS Code with the TOTVS Developer Studio extension, handling server setup, connection and compile result reporting.
Protheus Spec-Driven Development
totvs/engpro-advpl-tlpp-skills
Plans and builds Protheus AdvPL/TLPP features through Specify, Design, Tasks and Execute phases whose depth scales with the size of the change.
Protheus Data Dictionary Lookup
totvs/engpro-advpl-tlpp-skills
Queries the TOTVS Protheus ERP data dictionary for tables, fields, indexes, parameters, triggers and lookups, including impact checks during refactoring.
Protheus MVC Generator
totvs/engpro-advpl-tlpp-skills
Generates Protheus MVC screens in ADVPL/TLPP, with ModelDef, ViewDef, MenuDef and Browse functions for single-entity and master-detail layouts.
Query Builder
totvs/engpro-advpl-tlpp-skills
Build optimized and safe SQL queries for Protheus tables. An agent skill from totvs/engpro-advpl-tlpp-skills.
Related
Categories
Questions about AdvPL and TLPP Code Review
What does AdvPL and TLPP Code Review do?
Reviews AdvPL and TLPP source against SonarQube rules, ProtheusDOC requirements, security, performance and Protheus conventions, and reports findings by severity. prx extension are reviewed against TOTVS engineering standards, SonarQube static-analysis rules, ProtheusDOC documentation requirements and clean-code principles. The output is a categorized report with severity levels, rule references and fix suggestions that include code examples.
When should I use AdvPL and TLPP Code Review?
AdvPL and TLPP Code Review fits situations like: reviewing new or modified .prw, .tlpp or .prx files before merge; auditing legacy AdvPL code for SonarQube compliance; checking that ProtheusDOC blocks are complete and correct; looking for SQL injection or hardcoded credentials in Protheus code.
How do I install AdvPL and TLPP Code Review in Claude Code?
Run `npx skills add totvs/engpro-advpl-tlpp-skills --skill code-review -a claude-code`. Or copy the skill folder (skills/advpl-tlpp/code-review in totvs/engpro-advpl-tlpp-skills) into .claude/skills/code-review in your project. Claude Code loads it when a task matches its description.
How do I install AdvPL and TLPP Code Review in Codex?
Run `npx skills add totvs/engpro-advpl-tlpp-skills --skill code-review -a codex`. Or copy the skill folder (skills/advpl-tlpp/code-review in totvs/engpro-advpl-tlpp-skills) into .agents/skills/code-review in your project. Codex loads it when a task matches its description.
Can I use AdvPL and TLPP Code Review in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add totvs/engpro-advpl-tlpp-skills --skill code-review -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/code-review, .gemini/skills/code-review, .github/skills/code-review and .opencode/skills/code-review in your project.
What does AdvPL and TLPP Code Review need to run?
SKILL.md names no scripts, command-line tools or credentials: AdvPL and TLPP Code Review is instructions for the agent only.
Does AdvPL and TLPP Code Review access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is AdvPL and TLPP Code Review safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does AdvPL and TLPP Code Review use?
AdvPL and TLPP Code Review is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does AdvPL and TLPP Code Review use?
About 2.5k tokens (SKILL.md is roughly 10k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 4.3k tokens, read only when the agent opens those files.
What are the alternatives to AdvPL and TLPP Code Review?
Skills that share tags, products or a category with AdvPL and TLPP Code Review: Structured Code Review (FareedKhan-dev/claude-code-from-scratch, 298 stars), WooCommerce Code Review (woocommerce/woocommerce, 11k stars), Skill Doli Code Review (Dolibarr/dolibarr, 7.7k stars) and Dignified Python Standards (docling-project/docling, 68k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains AdvPL and TLPP Code Review?
totvs (a GitHub organization) maintains it in totvs/engpro-advpl-tlpp-skills, which has 141 GitHub stars. The repository holds 19 skills in this directory. The repository was last updated on October 5, 2026.
Source: totvs/engpro-advpl-tlpp-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.