بنقرة واحدة
init-memory
Manually load erinra session context — use when the automatic startup hook didn't trigger the call
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Manually load erinra session context — use when the automatic startup hook didn't trigger the call
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | init-memory |
| description | Manually load erinra session context — use when the automatic startup hook didn't trigger the call |
| argument-hint |
Manual fallback to load erinra session context. Use this when the automatic SessionStart hook fired but the memory context was not loaded.
Check that mcp__erinra__context is available in your tools. If not, tell the user:
Erinra MCP server is not connected. Run
claude mcp add erinra -- erinra serve -s userand restart Claude Code.
Load context — use the batched context tool to retrieve taxonomy and relevant memories in a single call:
mcp__erinra__context({
queries: ["user preferences and instructions", "recent decisions and patterns"],
include_taxonomy: true,
content_budget: 2000,
limit: 10
})
This returns deduplicated memories across all queries within the content budget, plus the full taxonomy (projects, types, tags, relations, stats).
Confirm to the user that memory context has been loaded, and briefly summarize what was retrieved (number of memories, projects, types found).
Run parallel code review agents and consolidate findings into a unified report
Capture a follow-up idea or task as a work-item draft without interrupting current work. Use to quickly jot down something you think of mid-task so it gets tracked. Works with nibs, GitHub, Azure DevOps, or a Markdown fallback.
Take an under-specified work item and make it actionable — resolve its open questions through a short interview grounded in the code, and give it acceptance criteria. Use on a captured draft, or any item too vague to start on.
Reconcile what was built against what was planned, record decisions and deviations, close the item (a single phase or a whole plan), and file follow-ups for deferred work. Use after finishing a phase or plan to keep planned and actual from drifting apart.
Orchestrate execution of MULTIPLE nibs in one run. Selects a queue, understands the nibs collectively (including how they fit together), then chooses the best execution mechanism per cluster — single series agent, parallel fan-out, scripted workflow, or agent team — and dispatches with ONE approval gate. Use when the user wants to work several nibs together (in parallel or series) rather than one at a time. Complements /decaf-build:auto-dev and /decaf-build:auto-tdd (which handle a single nib).
Direct development with automated review. Plans implementation, executes via subagent, then auto-reviews. Use for work that isn't test-driven (UI, config, styling, infrastructure, scaffolding).