policyengine/fix-pr
skills/workflows/fix-pr-skill/SKILL.md
Use when the user invokes $fix-pr or asks Codex to apply fixes to a PolicyEngine PR based on $review-program findings, GitHub review comments, CI failures, or local review reports.
$ install --global
skillsauthnpx skillsauth add policyengine/policyengine-claude fix-prInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 20, 2026, 6:55 AM112.3s3 files scanned
SKILL.md
- name:
- fix-pr
- description:
- Use when the user invokes $fix-pr or asks Codex to apply fixes to a PolicyEngine PR based on $review-program findings, GitHub review comments, CI failures, or local review reports.
fix-pr
This is the Codex equivalent of the Claude /fix-pr command.
Treat the text after $fix-pr as the command arguments:
$fix-pr [PR_NUMBER_OR_SEARCH] [--local]
Before starting, read workflow.md and subagents.md. Follow them as the source of truth for phases, checkpoints, handoff files, verification, and Codex subagent delegation.
Operational rules:
- Determine the PR first, then ask whether to push and post unless
--localis set. - Do not read full review reports into the main context until the final display step. Use short handoff files.
- Write a fix plan before editing.
- Apply only fixes listed in the fix plan.
- Use PolicyEngine skills explicitly for fixes:
$policyengine-parameter-patterns,$policyengine-variable-patterns,$policyengine-testing-patterns,$policyengine-code-style,$policyengine-code-organization, and$policyengine-period-patterns. - This workflow is designed for Codex subagents. When subagent use is available and authorized, delegate issue gathering, scoped fixes, CI, verification, and comment writing using subagents.md; otherwise execute the fix workflow directly with the same handoff-file boundaries.
Related Skills
policyengine/policyengine-python-client
tools
VerifiedTrustedCommunity
ONLY use this skill when users explicitly ask about the PolicyEngine Python package installation, REST API endpoints, API authentication, rate limits, or policyengine.py client library. DO NOT use for household benefit/tax calculations — ALWAYS use policyengine-us or policyengine-uk instead. This skill is about the API/client tooling itself, not about calculating benefits or taxes.
29SKILL.mdUpdated Apr 28, 2026
policyengine/policyengine-microsimulation
development
VerifiedTrustedCommunity
ALWAYS USE THIS SKILL for PolicyEngine microsimulation, population-level analysis, winners/losers calculations. Triggers: microsimulation, share who would lose/gain, policy impact, national average, weighted analysis, cost, revenue impact, budgetary, estimate the cost, federal revenues, tax revenue, budget score, how much would it cost, how much would the policy cost, total cost of, aggregate impact, cost to the government, revenue loss, fiscal impact, poverty impact, child poverty, deep poverty, poverty rate, poverty reduction, how many people lifted out of poverty, SPM poverty, distributional impact, state tax, state-level, California, New York, UBI, universal basic income, flat tax, standard deduction, winners and losers, winners, losers, inequality, Gini, decile, SALT, marginal tax rate, effective tax rate. NOT for single-household calculations like "what would my benefit be" - use policyengine-us or policyengine-uk for those. Use this skill's code pattern; explore codebase for parameter paths if needed.
29SKILL.mdUpdated Apr 28, 2026
policyengine/policyengine-api-v2
development
VerifiedTrustedCommunity
PolicyEngine API v2 - Next-generation microservices architecture with monorepo structure
29SKILL.mdUpdated Apr 28, 2026
policyengine/python
development
VerifiedTrustedCommunity
ALWAYS LOAD THIS SKILL before setting up any Python environment or installing packages. Defines the standard: uv, Python 3.13, uv pip install, .venv at project root. Triggers: "set up python", "install python", "create a venv", "virtual environment", "pip install", "install packages", "uv pip", "uv venv", "python version", "VIRTUAL_ENV", "venv conflict", "which python", "activate", "deactivate", "run the script", "run with uv", "uv run", "pyproject.toml", "install dependencies", "install requirements", "install the package", "editable install", "pip install -e", "latest package", "latest version", "current version", "newest version".
29SKILL.mdUpdated Apr 28, 2026