rosy

Audit and update project documentation after code changes — README files, skills, the root CLAUDE.md, and memory. Use after any session that added/removed any statements or expressions, changed the build/test setup, or renamed things. Also use when the user says "update docs", "sync docs", "are the docs up to date", or "refresh documentation". Can be invoked proactively at the end of a work session when significant structural changes were made.

Use this skill for ANY interaction with the hiibolt/rosy GitHub project — issues, PRs, branches, the project board, or any reference to a GitHub issue number (#N). This includes: creating, reading, updating, closing, or commenting on issues; managing the project board (moving items, changing status/priority/size); creating, reviewing, or merging PRs; managing branches; searching issues; and starting work on an issue. Triggers on: "#N" (any issue number reference), "start #N", "work on #N", "pick up #N", "begin #N", "what's #N", "new issue", "create issue", "plan feature", "open a ticket", "move to ready", "close issue", "update the board", "check PR", "what's the status of #N", "add a comment", "assign to", "change priority", "create a branch", "link PR", "open PR", "merge PR", "review PR", or any reference to GitHub issues, PRs, or the project board. Also triggers when the user describes a problem, idea, or change that should become a tracked work item — even casually phrased. When in doubt, trigger this ski