review

Solid

End-of-session orchestrator. Audits the session, then recommends the core save and session skills plus the rest — always asks before running anything, never auto-runs. Add the explicit '--full' flag to close a session in one command: the flag itself is consent, so it audits from the session's origin, then chains save → session → connect and runs a grounded verify pass with no per-skill prompts. Triggers on 'что забыли', 'что осталось', 'что ещё осталось', 'что ещё тут осталось', 'что осталось добить', 'что надо добить', 'что ещё надо добить', 'закрой сессию начисто', 'прогони весь цикл закрытия', 'одной командой закрой сессию', 'session review', 'ревью сессии', 'сессия ревью', 'что добить до идеала', 'all done', 'review --full', end of significant work, or similar. The ONLY command users need at session end — one confirmation covers everything, or '--full' covers it with none.

AI & Automation 6 stars 0 forks Updated today MIT

Install

View on GitHub

Quality Score: 81/100

Stars 20%
28
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# mn:review — Skill-Aware Session Completeness Analyzer > **Invocation marker (both runtimes):** begin your reply with the exact line `🧠 mn:review (mnemo) → running` — the user-visible confirmation that this skill actually loaded. Emit it once per invocation, before any other output. ## Portable paths Resolve `<mnemo-root>` once to the absolute plugin root before reading bundled files or running bundled scripts. In Claude Code, use `${CLAUDE_PLUGIN_ROOT}`; in Codex, derive it from this loaded `SKILL.md` path (skill directory → `skills/` → plugin root). Replace `<mnemo-root>` with that quoted absolute path in every command — never execute the placeholder literally and never hunt versioned cache directories. When another mnemo skill must run, use the runtime-native path: Claude Code invokes `mn:<skill>` through its Skill tool; Codex reads `<mnemo-root>/skills/<skill>/SKILL.md` completely and follows it with the prepared input. For user-facing explicit syntax, render `/mn:<skill>` in Claude Code and `$mnemo:<skill>` in Codex. You are performing a thorough end-of-session review. Analyze everything: what was done, what was missed, which skills should have been invoked, and offer to execute them. > **Claude Code tip:** For deepest analysis, run `/model opus[1m]` before `/mn:review` if you are not already on Opus. Codex uses the model selected for the current task. ## Workflow ### Step 0: Collect Evidence Use the runtime's normal tools to collect fresh evidence. Do not rel...

Details

Author
jojoprison
Repository
jojoprison/mnemo
Created
4 months ago
Last Updated
today
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Solid

session-review

End-of-session orchestrator. Audits the session, then recommends core skills (mnemo:memory-routing, mnemo:session-notes) and the rest — always asks before running anything, never auto-runs. Triggers on 'что забыли', 'что осталось', 'что ещё осталось', 'что ещё тут осталось', 'что осталось добить', 'что надо добить', 'что ещё надо добить', 'session review', 'ревью сессии', 'сессия ревью', 'что добить до идеала', 'all done', end of significant work, or similar. The ONLY command users need at session end — one confirmation covers everything.

6 Updated today
jojoprison
Code & Development Solid

session-review

End-of-session adversarial review loop. Assemble the session's work into a role-assigned, self-contained brief, then run independent reviewers in parallel — an isolated code-reader (the idea-validator agent) that reads the ACTUAL files and web-checks technology currency, plus an external-family model if you have one — synthesize where they agree vs diverge, apply the cheap-safe fixes immediately, record a measurable plan for the rest, and CHALLENGE reviewer claims you disagree with (never blind-accept). Use at the close of a substantive coding or design session, when the user says "session review", "review my session", "stress-test this session", or types /session-review. Skip for trivial one-off edits.

27 Updated 1 weeks ago
awrshift
AI & Automation Solid

session

Use when significant work wraps up — a feature shipped, a bug fixed, a research thread finished, before the user steps away — and also mid-task as a checkpoint before a long run risks context compaction (it updates the same session note + handoff, never spawns a duplicate). Also on 'записать сессию', 'сохрани сессию', 'отложи сессию в память', 'сессию в обсидиан', 'закругляйся с сессией', 'session note', 'handoff', or similar. Writes a human-readable summary plus a handoff so the next session picks up where you left off.

6 Updated today
jojoprison