Skip to content

Conversation

@policyengine
Copy link
Contributor

@policyengine policyengine bot commented Dec 9, 2025

Summary

Captured learning from working on policyengine-uk PR #1238 (renaming variables to lowercase).

The maintainer emphasized being "super careful" because variable/function renaming has "high potential to break things" even when most important variables already follow conventions.

Changes

Added new section to policyengine-review-patterns-skill covering:

  • Test Coverage Requirements: Unit tests, microsim tests, notebooks
  • Common Breakage Points: String references, dynamic lookups, API dependencies
  • Validation Strategy: Concrete commands to validate changes
  • Approval Requirements: Need maintainer review even when tests pass

Why This Matters

Large-scale refactoring operations can break things through:

  • Variables referenced as strings in reforms/API endpoints
  • Dynamic variable lookups via entity(variable_name, period)
  • Parameter files referencing variable names
  • External tools depending on naming conventions

This guidance helps future Claude Code sessions understand the validation requirements for these high-risk operations.

🤖 Generated with Claude Code

Captured learning from PR #1238 in policyengine-uk where maintainer
emphasized that variable/function renaming has "high potential to break
things" and requires careful validation.

Added section covering:
- Test coverage requirements for renaming operations
- Common breakage points (string references, dynamic lookups, etc.)
- Validation strategies (tests, notebooks, grep for references)
- Approval requirements even when tests pass

This guidance helps future Claude Code sessions understand the risks
and validation needs for large-scale refactoring operations.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants