Claude Skills by A

Cut a booping plugin release — verify the version bump against the last published tag, draft public-voiced release notes, merge the release branch into master, tag, and publish the GitHub release. Use when cutting a vX.Y.Z release of this repo.

Run a user-authored playbook from the vault: a multi-step guided procedure. Lists available global and local playbooks, selects one by trigger, and drives its steps in order — spawning per-step sub-agents or running inline, pausing at review gates.

A skill with debug mode enabled

A sample skill for testing

Authoring or refactoring a Claude Code skill — skill bodies, partials, config schema, rendered outputs, skill-level agents.

Context-aware chat about the project: discuss plans, retros, lessons, and code; navigate the vault; and handle chores (frontmatter tweaks, status flips, inline plan or code edits) without invoking the heavier skills. Opens every session with a vault status summary.

Review changed code (diff, files, or directory) against layered, stack-aware checklists plus plan- and lesson-aware dynamic checks. Stateless side-skill — chat-only output, no plan-lifecycle status, no persistent report.

Execute a groomed plan milestone-by-milestone via sub-agents. Use after /groom produces a plan file that is ready to implement.

Deep-research a feature, bug, or refactor and produce a specified, estimated plan with Definition of Done. Cross-validates architecture with a second model when useful. Use when the user describes a new piece of work that needs to be shaped before implementation.

Show what booping is, the available commands, and how to use them. Use when the user asks for help, wants a tour of the plugin, or is onboarding.

Scaffold a booping project under ~/Claude/{project}/ and attach it to the current repo. Use when onboarding a new repo or formalizing an existing one.

Extract lessons from a retrospective and fold improvements into project-local skill/agent extensions under _booping/. Use after /retro writes a retrospective.

Generate a project- and plan-specific sprint retrospective by reviewing session logs, gathering user feedback, and comparing plan vs built. No cross-project generalization or candidate lessons. Use after /develop reports a sprint DONE, or when the user explicitly asks to retro a plan.