---
name: Code Explanation
slug: code-explanation
category: Writing
description: Code Explanation helps explain existing ADVPL/TLPP routines in plain language for junior developers, senior developers, or functional consultants. Use it to understand legacy code, assess a customization, or fill gaps in documentation.
github: "https://github.com/thalysjuvenal/advpl-specialist/tree/main/skills/code-explanation"
language: Shell
stars: 186
forks: 37
install: "npx degit https://github.com/thalysjuvenal/advpl-specialist/tree/main/skills/code-explanation ~/.claude/skills/code-explanation"
installs_to: ~/.claude/skills/code-explanation
source_path: skills/code-explanation/SKILL.md
collection_size: 18
category_size: 1279
collection_url: "https://dirskills.com/collections/thalysjuvenal/advpl-specialist"
added: 2026-09-06T05:20:28.280Z
last_synced: 2026-09-06T05:20:28.280Z
canonical_url: "https://dirskills.com/skills/code-explanation"
---

# Code Explanation

Code Explanation helps explain existing ADVPL/TLPP routines in plain language for junior developers, senior developers, or functional consultants. Use it to understand legacy code, assess a customization, or fill gaps in documentation.

**Install:**

```bash
npx degit https://github.com/thalysjuvenal/advpl-specialist/tree/main/skills/code-explanation ~/.claude/skills/code-explanation
```

## README

# ADVPL/TLPP Code Explanation

This skill provides a methodology for explaining existing ADVPL/TLPP code in plain language, tailored to three audience levels: a junior developer needing line-by-line detail, a senior developer needing a business-logic summary with risks and technical debt, and a functional consultant needing a non-technical description of what the routine does from a business perspective.

Activate this skill when the user wants an existing routine, function, or snippet explained -- e.g. onboarding a new developer, understanding legacy code with no documentation, or briefing a functional consultant on a customization. It reads the target code, determines the requested (or asked) explanation level, and structures the output accordingly, optionally pulling in native-function meanings, business-process context, or SQL details as needed.

It does not cover generating formal documentation artifacts like Protheus.doc headers or full routine specs (see `documentation-patterns`), looking up native function syntax in isolation (see `protheus-reference`), or explaining embedded SQL macro semantics in depth (see `embedded-sql`).

| Reference file | Read when |
|---|---|
| reference.md | Always -- explanation levels, structure per level (junior/senior/funcional), and the analysis process |