check-initialisation
Use only when the user invokes /check-initialisation or asks to verify, repair, align, migrate, or finish this project's memory initialization.
- License 许可
- MIT
- 最近更新
- 2026-07-19
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- check-initialisation
- description
- Use only when the user invokes /check-initialisation or asks to verify, repair, align, migrate, or finish this project's memory initialization.
03 SKILL.md 正文
Check Initialisation
Follow the project AGENTS.md memory directives. This skill is a project-local shortcut; it does not override project instructions.
Steps
- Confirm required memory files exist:
memory/index.mdmemory/devices.mdmemory/runs.mdmemory/learnings.mdmemory/decisions.mdmemory/notes/memory/scratch/index.mdmemory/integrations/index.md
- Confirm consolidated project-local memory skills exist for
remember,scratch,organise-scratch, andcheck-initialisationunder both.agents/skills/and.claude/skills/. - Confirm
AGENTS.mdcontains exactly one project memory block. - Confirm
CLAUDE.mdis a regular file whose first non-empty line is exactly@AGENTS.md, unless the user explicitly asked to skip it. - Treat old direct-name skills and
memory/commands/as compatibility surfaces. Remove exact-template copies only afterremembercovers their behavior; preserve/report custom instructions. - If provider-specific integration files exist, align their local folders and drafts/ledgers without requiring external tools or authentication.
- Align missing memory infrastructure when it is safe to do so, preserving all existing project instructions and memory content.
- If existing instructions conflict or preservation is ambiguous, stop and ask the user.
- Do not stage, commit, or push unless the user explicitly asks from this project repository.
Report
Report whether initialization is correct, what was aligned, and any remaining issue.
04 同仓库更多 Skills
status
Use only when the user invokes /status or explicitly asks to update the project memory context card, blocker, latest result, or next action. Do not use for ordinary git status unless the user asks to log project status in memory.
scratch
Use only when the user invokes /scratch or explicitly asks to capture uncertain, in-flight, project-local working notes that are not ready for durable memory.
run
Use only when the user invokes /run or explicitly asks to record or update an experiment, evaluation, benchmark, or long-running job in project memory. Do not use for executing shell commands, running tests, or starting ordinary programs unless the user asks to log that run in memory.
remember
Use only when the user invokes /remember or asks to record project activity, a run, decision, learning, status change, blocker, next action, or compact daily memory. Do not use for unrelated reminders or task scheduling.
organise-scratch
Use only when the user invokes /organise-scratch or asks to route project-local scratch notes into durable project memory files.
log
Use only when the user invokes /log or explicitly asks to record session work or a meaningful project change in project memory. Do not use merely to inspect application logs.