Migrate SAS programs to Python, Java, or Postgres with operational fidelity verification.
npx skills add https://github.com/pjherron/hypoc --skill sas-migration-pjherron
Please help me install this Agent Skill. Skill: sas-migration Source: https://github.com/pjherron/hypoc/tree/main/hypoc/skills/sas-migration Command: npx skills add https://github.com/pjherron/hypoc --skill sas-migration-pjherron
High-intent search queries and answers about installing and using this skill.
Inventory all DATA steps, PROC steps, macros, and library references, then map DATA steps to pandas or polars, PROC SQL to Postgres or SQLAlchemy, and macros to Python functions. Document every point where Python behavior diverges from SAS as a fidelity risk.
Operational fidelity means the migrated system does the same job in production: reports are correct and QC checkpoints are trustworthy. It is the acceptance criterion rather than byte-for-byte output parity with the original SAS program.
Each checkpoint in the SAS program must have a named equivalent in the migrated code, extractable at the same logical pipeline point. Document the mapping as SAS checkpoint name to migrated equivalent to extraction method.
Yes, PROC SQL maps to Postgres queries or SQLAlchemy in Python. SAS formats and informats need Python equivalents with notes on divergence, since missing value handling, sorting defaults, and date formats can differ.
Log hours per phase: inventory, mapping, implementation, and verification. Record complexity signals like macro count, external library dependencies, checkpoint count, and data volume to feed the cost re-estimation model for remaining programs.
pwwangLoad, preprocess, and integrate multi-sample scRNA-seq data into a Seurat object.
anton-abyzovGenerate Terraform or Pulumi code for Hetzner Cloud infrastructure.
riethmayerMaintain a persistent execution loop with retries and architect sign-off before completion.
xiaosongzTranslate SAS study descriptions into SAS 9.4 programs and review code for common pitfalls.
