Menu
Ensure files are re-read before editing to avoid overwriting user changes. Use only when explicitly encouraged to by user.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | reread-files-before-editing |
| description | Ensure files are re-read before editing to avoid overwriting user changes. Use only when explicitly encouraged to by user. |
Before editing any file, re-read it to ensure you are using the latest version.
This is a one-time freshness check for the current operation. Do not assume previously read file contents are still valid if the user may have edited them.
The user may modify files outside your current context. Using stale content can overwrite those changes.
Before making an edit:
User-owned external project notes in ~/.field_notes. Use when the user asks to check, search, read, save, append, update, or consult field notes; phrases include "check field notes", "look in field notes", "save to field notes", "what do field notes say", "what's next", progress notes, planning notes, external docs, cross-project memory, or docs that should live outside a repository.
Style review notes for UI/design work. Use when reviewing or implementing visual style, layout, components, typography, icons, cards, themes, or dark mode. Bias toward minimal, simple interfaces with a slight note of whimsy.
Control the user own Chrome browser via Playwriter extension with Playwright code snippets in a stateful local js sandbox. Use this over other Playwright MCPs to automate the browser — it connects to the user's existing Chrome instead of launching a new one. Use this cli for navigating JS-heavy websites (Instagram, Twitter, cookie/login walls, lazy-loaded UIs) instead of webfetch/curl. ALWAYS load this skill before using any playwriter commands
Open and drive Pi's HTML Super Review UI for uncommitted changes or git ranges. Use when the user asks for super-review, review current changes, review against master/origin, or read comments from the review UI.
Rebase a feature worktree on main/master, resolve conflicts, ff-only merge into the trunk worktree, then rebase feature on updated trunk.
Guide for using the Sentry CLI to interact with Sentry from the command line. Use when the user asks about viewing issues, events, projects, organizations, making API calls, or authenticating with Sentry via CLI.
