project-consolidate-source

Audit Pascal/Delphi/FPC projects for header, module, and build configuration issues.

Updated Jan 6, 2026

Search Tags:#audit #code-quality #build-config #module-architecture #fpc #delphi #pascal

Ready to run

npx skills add https://github.com/cslsoftwares/ParamentersORM --skill project-consolidate-source

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: project-consolidate-source
Source: https://github.com/cslsoftwares/ParamentersORM/tree/main/.cursor/skills/project-consolidate-source_V1.0.0
Command: npx skills add https://github.com/cslsoftwares/ParamentersORM --skill project-consolidate-source

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a read-only, standards-based audit of Pascal/Delphi/FPC project sources to identify header deviations, module structure issues, naming inconsistencies, and build configuration problems.

Core Features & Use Cases

Six checks cover standard header verification, broken uses, modular MXX structure, naming conventions, dry-run build validation, and Git ignore compliance.
Use cases include auditing repositories before merges or releases to surface non-conformities and generate a remediation report for developers.

Quick Start

Run the project-consolidate-source audit on a repository to generate a Markdown report outlining header, module, and naming non-conformities.

Frequently Asked Questions about project-consolidate-source

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I audit Pascal project source code for header and naming non-conformities?▼

Auditing Pascal source code involves validating headers, uses references, and naming conventions across .pas, .dpr, and .lpr files. This process detects module structure issues and build configuration problems, generating a consolidated Markdown report with actionable remediation recommendations.

What does a read-only Delphi project audit check for in a repository?▼

A read-only Delphi audit performs six checks covering standard header verification, broken uses references, modular MXX structure, naming conventions, dry-run build validation, and Git ignore compliance to surface non-conformities before merges or releases.

Can I check FPC build configuration and module structure without modifying my project?▼

Yes, you can perform a read-only audit on FPC projects targeting .lpr and .lpi files. It validates build configurations and module structures safely without modifying the repository, producing a Markdown report outlining detected issues.

How do I validate .dproj and .lpi build configurations before a release merge?▼

Validating .dproj and .lpi build configurations requires running a standards-based audit that performs dry-run build validation and Git ignore compliance checks. This surfaces configuration problems and outputs a remediation report for developers.

What is the best way to generate a remediation report for Free Pascal repository issues?▼

The best way is running an automated audit that checks headers, module architecture, and naming conventions in Free Pascal repositories. It produces a consolidated Markdown report with actionable recommendations for fixing detected non-conformities.

Does this Pascal code audit fix broken uses references and header deviations automatically?▼

No, the audit is strictly read-only and does not modify code. It detects header deviations, broken uses, and naming inconsistencies, generating a Markdown report with actionable recommendations for developers to apply manually.