Claude-Mem Post-release Verification

thedotmack/claude-mem

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

Contenu mis à jour:

Dans la collectionClaude-Mem ↗
Voir sur GitHub
npx claude-mem install
116 859Étoiles10 141ForksDernier push du dépôt

À propos de ce Skill

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

Pourquoi ce choix

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.

À quoi il sert

  • 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.

Avant de l’utiliser

  • 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.

Agents compatibles

Claude CodeCodex CLI

Sources et références

Les sources originales sont liées ci-dessous. Les pistes pratiques sont des suggestions de la rédaction de SkillHey.