skills.rest
ElPoot
ElPootCOMMUNITY
Explore all skills by this author →
GitHub

audit-release

Audit PyInstaller Windows release builds for reproducibility and dependency consistency.

Updated Feb 26, 2026
Search Tags:#versioning#release engineering#pyinstaller#dependency auditing#windows exe#hidden imports#build reproducibility
One-click install
npx skills add https://github.com/ElPoot/contabilidad --skill audit-release
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: audit-release
Source: https://github.com/ElPoot/contabilidad/tree/main/.agents/skills/audit-release
Command: npx skills add https://github.com/ElPoot/contabilidad --skill audit-release

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents broken or non-reproducible Windows release artifacts by auditing PyInstaller packaging, dependency inclusion, and version/release metadata directly from the repository source.

Core Features & Use Cases

  • PyInstaller release integrity checks: Verifies hidden imports, bundled datas/binaries/collect rules, exclusions, and whether packaging mode (onefile/onedir) is consistent with expectations.
  • Versioning and release traceability review: Confirms the source of versioning in gestor_contable/version.py, checks for tag/commit-version automation signals, and detects presence/absence of changelog history.
  • Dependency alignment validation: Compares requirements.txt declared dependencies against real Python imports and any hidden imports specified in the .spec.

Use case: Before publishing a new Windows executable for contabilidad, run this audit to ensure the build script, PyInstaller spec, and versioning/changelog signals are consistent and that no required runtime dependencies are missing from the packaged binary.

Quick Start

Ask the AI to run the audit-release checks on build.py, gestor_contable.spec, gestor_contable/version.py, and requirements.txt and then produce the release engineering report with a clear verdict.

Frequently Asked Questions about audit-release

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

FAQPage Schema
How do I check my PyInstaller spec for missing hidden imports before a Windows release?▼

PyInstaller hidden imports are validated by auditing the .spec configuration against real Python imports and requirements declarations. This process identifies missing runtime dependencies, bundled data rules, and exclusions to ensure consistent executable packaging.

Why does my PyInstaller Windows executable build fail with missing dependencies?▼

Missing dependencies in PyInstaller builds occur when requirements.txt declarations mismatch actual Python imports or .spec hidden imports. An audit compares these source files to detect unlisted runtime packages before publishing the Windows executable.

What's the best way to validate build reproducibility for a PyInstaller onefile or onedir release?▼

Build reproducibility is validated by auditing the .spec file's packaging mode (onefile/onedir), hidden imports, bundled binaries, and collect rules. This confirms the build script and spec configuration produce consistent Windows release artifacts.

How do I ensure versioning traceability in my Python release engineering workflow?▼

Versioning traceability is confirmed by checking version.py for the version source, detecting tag or commit-based automation signals, and verifying changelog presence. This audit ensures release metadata is consistent and traceable across builds.

Can I audit my requirements.txt against actual imports to find unused or missing packages?▼

Requirements auditing compares declared dependencies in requirements.txt against real Python imports and hidden imports from the .spec file. This detects mismatches where required runtime dependencies are missing or unused packages are declared.

When do I need to run a release engineering audit on my PyInstaller build pipeline?▼

A release engineering audit is needed before publishing any new Windows executable to verify build script consistency, spec configuration integrity, and dependency alignment. Run it when changes occur in build.py, .spec files, version.py, or requirements.txt.

Related Skills

Explore More Software Engineering Skills→
gajjalaashok75-UIgajjalaashok75-UI
2

python-packaging

Create, structure, build, and publish Python packages with pyproject.toml.

Community
Advanced
MathiasPaulenkoMathiasPaulenko

flet-desktop

Build and package cross-platform desktop apps with Flet and Python.

Community
Intermediate
murphytruemanmurphytrueman
155

cicd-integration

Generate CI/CD pipeline configurations for design system quality checks.

Community
Advanced
a2musa2mus

speckit-security-scan

Audit codebases for secrets, injection, CSRF/XSS, and dependency risks.

Community
Intermediate