.claude/skills/cure_release/SKILL.md
# `cure_release` This skill is a thin adapter for the repo-owned `cure_release` workflow. - Canonical workflow: [../../../operations/commands/cure_release.md](../../../operations/commands/cure_release.md) - Normative release policy: [../../../RELEASING.md](../../../RELEASING.md) If the adapter and `RELEASING.md` disagree, `RELEASING.md` wins. Do not duplicate the workflow here; execute the canonical command file instead.
npx skillsauth add grzegorznowak/cure .claude/skills/cure_releaseInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
cure_releaseThis skill is a thin adapter for the repo-owned cure_release workflow.
If the adapter and RELEASING.md disagree, RELEASING.md wins. Do not duplicate the workflow here; execute the canonical command file instead.
databases
Run GitHub pull request reviews in isolated sandboxes with CURe. Use when you need a safe, repeatable PR review workflow with `cure setup`, `cure pr`, `cure status`, `cure watch`, `resume`, and `zip`.
tools
Use when work should span one or more detached tasks but still behave like one job with a single owner context. TaskFlow is the durable flow substrate under authoring layers like Lobster, ACPX, plugins, or plain code. Keep conditional logic in the caller; use TaskFlow for flow identity, child-task linkage, waiting state, revision-checked mutations, and user-facing emergence.
tools
# Lobster Lobster executes multi-step workflows with approval checkpoints. Use it when: - User wants a repeatable automation (triage, monitor, sync) - Actions need human approval before executing (send, post, delete) - Multiple tool calls should run as one deterministic operation ## When to use Lobster | User intent | Use Lobster? | | ------------------------------------------------------ | --------------------------
tools
# Lobster Lobster executes multi-step workflows with approval checkpoints. Use it when: - User wants a repeatable automation (triage, monitor, sync) - Actions need human approval before executing (send, post, delete) - Multiple tool calls should run as one deterministic operation ## When to use Lobster | User intent | Use Lobster? | | ------------------------------------------------------ | --------------------------