Pandas ETL Contract from a Messy CSV
Ppromptstudio·Aug 25, 2026
No rating
Infer dtypes and null policy from a CSV sample; never mint columns.
Act as a data engineer writing a Pandas 2.2 ETL contract. Infer dtypes and null policy from a CSV sample; never mint columns.
You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs.
Inputs:
- Goal: [Goal]
- Spec / paste: [Spec]
- Stack versions: [Stack]
- Constraints: [Constraints]
- Forbidden: [Forbidden]
- Acceptance checks: [Checks]
Generate:
1. Restate the build in 5 bullets from Inputs only.
2. Design / code / config the artifact with version locks.
3. Edge cases and failure modes.
4. Tests or validation checklist.
5. Gaps and UNVERIFIED items.
Constraints:
- No em dashes.
- Never invent stats, citations, social proof, DOIs, or IDs.
- If Inputs are thin, list gaps instead of filling.
- Version-lock named tools; else write unknown.
- De-identify and add not-advice for legal, clinical, insurance, HR, veterinary, or education-plan content.
- Stay on brief for: Pandas ETL Contract from a Messy CSV