Claude-Mem Post-release Verification

Über diesen Skill

Check shipped packages, deployments, installed plugins, and late reports during a defined post-release observation window.

Warum wir es empfehlen

A reusable workflow from the Claude-Mem project. It is listed separately to explain this task; shared runtime and helper dependencies remain part of the upstream installation. The inherited gallery demonstrates the memory system, not this task’s specific output.

Wobei es hilft

• Verify what users receive after a release rather than stopping at a successful publish command.

How the workflow runs

1. Step 1

   Fix the release identity, affected surfaces, and observation window.

2. Step 2

   Check exact artifacts, real user paths, CI, and relevant reports.

3. Step 3

   Distinguish verified regressions from infrastructure gaps and report evidence and pending actions.

Original childhood instructions

Expected result

A release verification receipt with observation times, findings, and any unresolved coverage gaps.

Original childhood instructions

Try a concrete request

1. Example request

   After installing the required integration, ask your agent:

   Verify the deployed release and monitor its changed user path for thirty minutes.

Vor der Nutzung

• The shipped release identity, access to affected delivery surfaces and CI, and permission for any requested repair.
• Use the original upstream files and follow the documented host integration. Model or third-party service usage can carry separate costs.

Unterstützte Agents