메뉴
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.