(project) Use when updating install tasks in playbooks/roles/ against upstream docs — bumping a pinned version, adopting a newly recommended install method, repointing a doc link that moved, or realigning the community.general pin with the brew-installed…
Use when making any git commit. Always pass what was wrong before the changes as the argument; when nothing was wrong, pass what the changes do instead — never an invented why.
(project) Use when editing any file under skills/ or plugins/ to bump the plugin version and check the manifests
Use when the user explicitly asks to push the current branch and open a PR, rewrite an open PR's body from its commits, or wait for CI and merge it
Use when about to refactor or refine an existing skill, its SKILL.md or sibling files, from a full restructure down to a one-line wording fix; a change that looks too small to need this skill is not an exemption. Not for creating a skill from scratch
Use when auditing Claude Code settings and env vars against the latest docs to suggest tailored changes
Use when the user explicitly asks for simple English, plain English, or for text a non-native English speaker can read easily — rewrites docs, READMEs, issues, comments, or UI text into plain words and translation-friendly grammar, still native-sounding.…
Use when about to choose, configure, or refine a tool, library, config format, API pattern, or project setup, or before proposing a design of your own — research current guidance, pitfalls, and prior art first; already knowing an approach, or assuming no…