changelog-patterns
Skill183 starsChanged 2 months agoMITView on GitHub
Use when the user asks to generate a changelog, release notes, or delivery notes from ADVPL/TLPP code changes on TOTVS Protheus -- analyzing diffs or a list of changed files, classifying each change (NEW/FIX/CHANGE/REMOVE/REFACTOR), assessing business impact (ALTO/MEDIO/BAIXO), and detecting affected tables. Also triggers on Portuguese phrasing like "gerar changelog", "notas de versao", "documentar entrega", "o que mudou nessa versao", or requests to audit code changes for compliance.
In this repository21 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- advpl-code-generationSkill
- advpl-code-reviewSkill
- advpl-debuggingSkill
- advpl-refactoringSkill
- advpl-to-tlpp-migrationSkill
- advpr-test-automationSkill
- code-explanationSkill
- documentation-patternsSkill
- embedded-sqlSkill
- probat-testingSkill
- protheus-businessSkill
- protheus-locks-deadlocksSkill
- protheus-referenceSkill
- query-builderSkill
- smartview-developmentSkill
- smartx-developmentSkill
- sx-configurationSkill
- tdn-lookupSkill
The file
Files
Changelog Patterns
This skill defines how to analyze ADVPL/TLPP code changes (via git diff or a supplied file list) and produce a structured changelog: change type classification (NEW/FIX/CHANGE/REMOVE/REFACTOR with Portuguese labels), impact level assessment (ALTO/MEDIO/BAIXO), detection of affected database tables from DBSelectArea/RecLock/BeginSQL patterns, and output in either Markdown or plain-text format.
Activate this skill when the user wants a client-facing or internal changelog, release notes, or delivery documentation generated from a set of code changes. It does not cover generating documentation headers or technical routine specs from a single source file with no diff context -- that is closer to a documentation-generation task and out of scope for this skill's diff-analysis process; it also does not cover code review findings (see advpl-code-review) or the migration checklist for .prw to .tlpp conversions (see advpl-to-tlpp-migration).
| Reference file | Read when |
| reference.md | Always -- the only file in this skill; contains change types, impact levels, Markdown/TXT changelog formats, and the full analysis process |
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.