glm-plan-usage

Make one small, incremental code improvement to reduce codebase entropy. Use this skill whenever the user wants to nudge the codebase toward better shape, asks for a tiny refactor, says "nudge", or wants a low-risk cleanup pass — even if they don't describe a specific change.

Generate an end-to-end acceptance checklist by diffing the current codebase against the last released version. Compiles every user-facing and behavioral change into a structured, step-by-step verification manual. Use this skill whenever the user mentions "preflight", "acceptance testing", "acceptance manual", "release checklist", "verification checklist", "what changed since last release", or wants to validate readiness before shipping a new version. Also trigger when the user asks to review changes between versions or prepare QA steps.

Best practices for writing and organizing tests with pytest including fixtures, parametrize, and plugins.

Execute the glm-plan-usage release process. Use this skill when the user wants to publish a new version, create a release, bump version numbers, or says things like "release v0.2.0", "publish a new version", "cut a release", "ship it", or "prepare release". Also use when the user mentions CHANGELOG updates combined with version bumping in this Rust + NPM project.