菜单
Internal dogfooding skill for storing and recalling engineering context through the csm CLI during day-to-day development.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | skill-memory-internal |
| description | Internal dogfooding skill for storing and recalling engineering context through the csm CLI during day-to-day development. |
Use this skill when you want agents to persist operational context while implementing, fixing, testing, or planning.
export CSM_MEMORY_DB=".agents/csm-memory/skill-memory.db"
mkdir -p "$(dirname "$CSM_MEMORY_DB")"
Use stable IDs so later probes can find related entries:
skill::<skill_name>::<category>::<slug-or-timestamp>
Examples:
skill::impl::refactor::2026-04-12T08-22-10Zskill::fix::error-resolution::merge-conflict-overwritecsm --database "$CSM_MEMORY_DB" inject \
"skill::fix::error-resolution::load-merge-overwrite" \
--metadata '{"operation":"error_resolution","context":"load_merge conflict policy","result":"skip-on-conflict"}'
csm --database "$CSM_MEMORY_DB" probe "load merge overwrite policy" -k 5 --output-format json
csm --database "$CSM_MEMORY_DB" associate \
"skill::fix::error-resolution::load-merge-overwrite" \
"skill::test::regression::load-merge-no-overwrite" \
-s 0.9
operation, context, result, timestamp).# write
csm --database "$CSM_MEMORY_DB" inject "skill::internal::smoke::$(date +%s)" --metadata '{"smoke":true}'
# read
csm --database "$CSM_MEMORY_DB" probe "smoke" -k 1 --output-format json
If both commands succeed and return at least one result, internal memory is operational.
GOAP-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.