GLM plan usage plugin for Claude Code
This repository also configures its own agents. See what glm-plan-usage tells them →
Skill Claude Code
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
Skill Claude Code
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.
Skill Claude Code
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…
Skill Claude Code needs its repo
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…
Skill Claude CodeCodex
Best practices for writing and organizing tests with pytest including fixtures, parametrize, and plugins.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: