alignment-review
Alignment Review
Review code changes for alignment with OpenEnv principles using a two-tier model.
Instructions
-
Run automated checks first:
- Execute
bash .claude/hooks/lint.sh- capture lint issues - Execute
bash .claude/hooks/check-debug.sh- capture debug code
- Execute
-
Read alignment documents:
.claude/docs/PRINCIPLES.md- design principles.claude/docs/INVARIANTS.md- system invariants
-
Read open RFCs:
- Scan
rfcs/directory for all RFC files - Note the status of each RFC (Draft, In Review, Accepted, Implemented)
- Pay special attention to Draft and In Review RFCs - these represent active design discussions
- Scan
More from meta-pytorch/openenv
write-tests
Write failing tests from requirements. Invoke for each todo before /implement.
25simplify
Refactor code after tests pass. The "Refactor" phase of Red-Green-Refactor.
20pre-submit-pr
Validate changes before submitting a pull request. Run comprehensive checks including lint, tests, alignment review, and RFC analysis. Use before creating a PR, when asked if code is ready for review, or before pushing for PR.
20rfc-check
Determine if proposed changes require an RFC. Use when planning significant changes, before starting major work, or when asked whether an RFC is needed.
19implement
Make tests pass. Invoke after /write-tests produces failing tests.
17work-on-issue
Start work on a GitHub issue. Extracts requirements, creates worktree, sets up TDD workflow.
17