PolicyEngine / PolicyEngine/policyengine-claude

18 skills/commands still reference old Microsimulation API instead of policyengine.py Simulation

Open
#116 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
32
Forks
6
PR merge metrics
No merged PRs in 30d

Description

The codebase has moved to policyengine.py with from policyengine.core import Simulation, ensure_datasets(), etc. But 18 files still reference the old Microsimulation class from policyengine_us/policyengine_uk:

  • skills/tools-and-apis/policyengine-microsimulation-skill/SKILL.md
  • skills/tools-and-apis/policyengine-interactive-tools-skill/SKILL.md
  • skills/technical-patterns/policyengine-vectorization-skill/SKILL.md
  • skills/technical-patterns/policyengine-testing-patterns-skill/SKILL.md
  • skills/technical-patterns/policyengine-review-patterns-skill/SKILL.md
  • skills/domain-knowledge/policyengine-us-skill/SKILL.md
  • skills/domain-knowledge/policyengine-uk-skill/SKILL.md
  • skills/domain-knowledge/policyengine-healthcare-skill/SKILL.md
  • skills/documentation/policyengine-writing-skill/SKILL.md
  • skills/documentation/policyengine-plugin-maintenance-skill/SKILL.md
  • skills/data-science/policyengine-us-data-skill/SKILL.md
  • skills/data-science/policyengine-uk-data-skill/SKILL.md
  • skills/analysis/policyengine-district-analysis-skill/SKILL.md
  • skills/analysis/policyengine-analysis-skill/MICROSIMULATION_REFORM_GUIDE.md
  • skills/README.md
  • commands/backdate-program.md
  • agents/country-models/implementation-validator.md
  • ECOSYSTEM.md

The only skill with correct imports is policyengine-simulation-mechanics-skill. All others should be updated to use from policyengine.core import Simulation and ensure_datasets() patterns.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with skills/tools-and-apis/policyengine-simulation-mechanics-skill/SKILL.md, the only listed skill described as having correct imports, then search the 18 named Markdown files for Microsimulation references. Update those references to the stated Simulation and ensure_datasets() patterns, and consider the work done when no outdated API references remain in the listed files.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.