config

Maintain repo documentation and markdown trackers so they stay concise, current, and authoritative. Use when Codex edits or reviews `README.md`, `AGENTS.md`, `docs/*.md`, onboarding notes, code comments, `todo.md`, `dev/todos.md`, PR cleanup docs, or other markdown guidance/task files, especially after technical changes, migrations, deprecations, or drift cleanup. Enforce open-items-only trackers, current-state-only docs/comments, canonical-source examples, and deletion of obsolete duplicate notes/specs.

Guide for working with grepo, a Rust CLI that manages project-local read-only reference repositories. Use this skill whenever a project contains a `.repos/` directory (or legacy `grepo/`) with a `.lock` file, when entries under `.repos/` appear as symlinks into a shared cache, when the user mentions grepo / `grepo add` / `grepo sync` / `grepo update`, or when you notice that code you are reading lives inside a read-only snapshot tree under `.repos/`. Explains the commands, the lockfile, sources (git URL / npm / cargo), and what the symlinked trees actually are.

Context for editing Tom's personal global config repo. Use when the user mentions changing or modifying personal/global config, dotfiles, Codex/Claude config, agent skills, Neovim config, Home Manager, nix-darwin, GNU Stow setup, or files that live under ~/.codex, ~/.claude, ~/.config, or ~/config outside a project-specific repo.

Write and edit in GOV.UK / GDS house style — plain English, active voice, front-loaded content, sentence case, and no bold or italics for emphasis. Use when writing or editing reports, research write-ups, guidance, documentation, summaries, or any prose where clarity and accessibility matter.