🧳 pybundle

---

Why pybundle?

pybundle exists to solve a boring but expensive problem:

Context loss.

Modern debugging, CI, audits, and AI-assisted workflows fail not because tools are weak — but because context is fragmented, ephemeral, or missing entirely.

pybundle creates a single, deterministic artifact that captures:

• the exact source code that mattered
• the tools that ran (and their versions)
• the environment they ran in
• the outputs they produced
• and the metadata required to reproduce or reason about it later

For humans, automation, and AI.

Think:

git archive + diagnostics + metadata without heuristics, guesswork, or “works on my machine.”

---

What pybundle is good at

pybundle is designed for:

• handing a project to another engineer
• attaching full context to a bug report
• generating CI artifacts that actually explain failures
• feeding codebases to AI tools without noise
• audits, reviews, and reproducibility
• answering “what exactly did we run?” weeks later

It prioritizes determinism, traceability, and automation over cleverness.

---

Installation

pip install gwc-pybundle

Note: The PyPI package name is gwc-pybundle, but the CLI command is pybundle.

Quick sanity check:

pybundle version

---

Where to go next

📚 Documentation (Wiki) ➡ https://github.com/girls-whocode/pybundle/wiki

The Wiki contains:

• Usage and profiles
• Security & redaction
• JSON output contracts
• CI integration
• AI handoff workflows
• FAQs and design rationale

💬 Questions & Discussion ➡ https://github.com/girls-whocode/pybundle/discussions

Use Discussions for:

• “Is pybundle right for this?”
• Workflow questions
• Design feedback
• Feature ideas
• Real-world use cases

---

Philosophy

If a tool produces output, it should also produce metadata explaining how and why that output exists.

pybundle treats context as a first-class artifact.

---

License

MIT License