0a-project-bootstrap-audit

Audit new Python project bootstrap structure and write findings to docs/todo.md.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/AgustinMadygraf/skills --skill 0a-project-bootstrap-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 0a-project-bootstrap-audit
Source: https://github.com/AgustinMadygraf/skills/tree/main/0a-project-bootstrap-audit
Command: npx skills add https://github.com/AgustinMadygraf/skills --skill 0a-project-bootstrap-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Performs an initial bootstrap audit to validate the base project structure and to surface actionable findings in docs/todo.md.

Core Features & Use Cases

  • Validates the base layout: required directories, essential files, and .gitkeep usage in empty directories.
  • Checks environment setup: presence of .env and .env.example and parity of environment keys.
  • Python project hygiene: ensures init.py exists in src subdirectories (excluding pycache and data).
  • Produces a structured report that can be written to docs/todo.md for stakeholder visibility.

Quick Start

Run the bootstrap gate against the repository root to audit the base structure and generate docs/todo.md.

Frequently Asked Questions about 0a-project-bootstrap-audit

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

FAQPage Schema
How do I validate my Python project structure after initial setup?

To validate your Python project structure, run a bootstrap audit against your repository root to verify required directories, essential files, and environment configuration. This process generates a structured report of any layout gaps or missing files for immediate correction.

What does a project bootstrap audit check for in a new Python repository?

A project bootstrap audit checks for required directories, essential files, proper .gitkeep usage in empty folders, and __init__.py presence in src subdirectories. It also validates environment setup by verifying .env and .env.example key parity.

How do I check if my .env and .env.example files have matching keys?

To check if your .env and .env.example files have matching keys, use a bootstrap audit tool that verifies environment variable parity. This ensures your environment configuration files contain the exact same keys to prevent missing variable errors during deployment.

Can I output my project audit findings directly to a markdown file?

Yes, you can output your project audit findings directly to a markdown file using the optional write-to-todo functionality. This generates a structured report at docs/todo.md, providing stakeholder visibility into your project's bootstrap gaps and required fixes.

Does the bootstrap audit verify __init__.py files in all Python subdirectories?

The bootstrap audit verifies __init__.py files in src subdirectories to ensure proper Python package recognition, but it explicitly excludes the __pycache__ and data directories from this check. This targeted validation maintains project hygiene without flagging non-package folders.

What is the best way to surface missing files and layout gaps in a new Python project?

The best way to surface missing files and layout gaps in a new Python project is to run an automated bootstrap audit that enforces required directories and essential files. This generates a stakeholder-ready report detailing structural violations and environment mismatches.