mcpField
C
code-explanation

code-explanation

github.com/thalysjuvenalDevelopment19352 installsUpdated 7w ago
Repository

About code-explanation

An explanation skill for existing ADVPL and TLPP code, for developers and functional consultants who need to understand routines or snippets. It adapts explanations to junior, senior, or non-technical audiences and can include relevant native-function, business-process, or SQL context.

Key features

  1. 01Explanations for three audience levels
  2. 02Line-by-line junior-level detail
  3. 03Senior-level logic and risk summaries
  4. 04Business-focused consultant explanations
  5. 05Optional native-function and SQL context

Use cases

  1. 01Onboarding developers to existing code
  2. 02Understanding undocumented legacy routines
  3. 03Briefing consultants on customizations

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/thalysjuvenal/advpl-specialist --skill code-explanation

After installing, type/code-explanationin Claude Code to confirm it loaded.

Bundled filesreference.md

Details

From the project 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 fileRead when
reference.mdAlways -- explanation levels, structure per level (junior/senior/funcional), and the analysis process

Comments

Markdown supported