القائمة
Portable verification skill for memory lifecycle operations (save, load, archive, delete) with file-level and database-level checks.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | memory-lifecycle-verification |
| description | Portable verification skill for memory lifecycle operations (save, load, archive, delete) with file-level and database-level checks. |
Use this skill when validating memory behavior across repositories or before release.
Prove that lifecycle operations are correct and auditable for both:
Set these variables per target codebase:
DB_PATH="${DB_PATH:-.tmp/memory-lifecycle.db}"
ARTIFACT_DIR="${ARTIFACT_DIR:-.tmp/memory-artifacts}"
mkdir -p "$ARTIFACT_DIR"
csm --database "$DB_PATH" inject "test::lifecycle::alpha" --metadata '{"phase":"save","v":1}'
csm --database "$DB_PATH" inject "test::lifecycle::beta" --metadata '{"phase":"save","v":1}'
csm --database "$DB_PATH" associate "test::lifecycle::alpha" "test::lifecycle::beta" -s 0.9
Expected:
probe can find test::lifecycle::alphacsm --database "$DB_PATH" export -o "$ARTIFACT_DIR/export.json"
csm --database "$ARTIFACT_DIR/roundtrip.db" import "$ARTIFACT_DIR/export.json"
csm --database "$ARTIFACT_DIR/roundtrip.db" probe "test::lifecycle::alpha" -k 3 --output-format json
Expected:
If native archive command exists, use it. Otherwise write an archive marker concept:
csm --database "$DB_PATH" inject "archive::test::lifecycle::alpha" \
--metadata '{"status":"archived","target":"test::lifecycle::alpha"}'
Expected:
Use native delete command when available. If not available, run retention policy that tombstones the concept.
Expected:
Capture all of the following:
references/VALIDATION_CHECKLIST.mdreferences/sql_checks.sqlGOAP-based orchestrator for managing GitHub issues, creating action plans, and executing workspace operations with branch/PR workflow.
Configure and troubleshoot npm OIDC Trusted Publishing for GitHub Actions. Use when npm publish fails with E404, OIDC errors, or provenance issues.
GitHub release management, crates.io trusted publishing, npm provenance, and GitHub Pages documentation. Use when creating releases, publishing packages, or deploying docs.
Git commit conventions, validation gates, and CI/CD workflows. Use when committing changes, verifying gates, or working with GitHub Actions.
Validate merge readiness with atomic commits and GitHub Actions checks using gh CLI; use for pre-merge verification and CI truth validation.
Apply TRIZ inventive principles to solve problems that seem to have no good solution. Use after triz-analysis has identified contradictions.