# Review Change

> Use when asked to review a new incoming change or PR in this Web Research / Truffle project.

- Skill: `brianbolze/review-change` (Agent Skill)
- Install (CLI): `npx skillmds@latest add brianbolze/review-change`
- Raw SKILL.md: https://api.skillmd.com/api/skills/brianbolze/review-change/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Research & Search
- Author: brianbolze (https://skillmd.com/u/brianbolze)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/brianbolze/review-change

---


$ARGUMENTS

- Review [`MAINTAINING.md`](../../../documentation/MAINTAINING.md)
- Review [engine-dev rules](../../rules/engine-dev.md). Are we adhering to them?
- Consider running the `drift-sweep` skill
- Consider looking at this from the perspectives of the different [personas](../../../documentation/personas.md)
- Look at the impact on the directory / file structure. Does this add bloat?
- Does this new change suffer from overfitting? Was it designed based on only a small set of data / specific circumstance?
- Does this new change increase complexity / risk in a way that we haven't anticipated?
- If this new feature / change has an associated "FRAME" doc - read it - and ensure we're meeting it's intended goals.
- If this new feature / change has an associated "PROPOSAL" / "APPROACH" doc - read it - and see if it has drifted.
- If the review surfaced a process friction, a recurring miss, or a Truffle gap worth remembering, log it as an observation per [`learning/AGENTS.md`](../../../experiments/01-agentic-build/learning/AGENTS.md) — capture only (never a fix); the review pass decides what to do with it.