end

End MARVIN sessions by saving context and committing changes.

Updated Feb 3, 2026
One-click install
npx skills add https://github.com/gaodes/marvin --skill end-gaodes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: end
Source: https://github.com/gaodes/marvin/tree/main/skills/end
Command: npx skills add https://github.com/gaodes/marvin --skill end-gaodes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

End MARVIN sessions by preserving the full conversation context, logging outcomes, and optionally committing changes to the project logs.

Core Features & Use Cases

  • End a session and preserve the current context for future reference.
  • Generate and persist session logs in content and session logs.
  • Commit changes to git or a configured VCS if requested.

Quick Start

End the current session and persist the context to logs and state.

Frequently Asked Questions about end

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I end a session and preserve conversation context for future reference?

To preserve context when ending a session, this Skill aggregates current session data and updates content and session logs. It refreshes the current state to ensure your conversation context is saved for future reference.

Can I automatically commit changes to git when ending a development session?

Yes, you can automatically commit changes to git when ending a session. The Skill optionally commits changes to a configured VCS or repository, aggregating session data and updating logs while performing the git commit.

What is the best way to log session outcomes and update project state?

The best way to log session outcomes is by triggering the end session command, which aggregates session data, updates session logs, and refreshes the current state. This preserves your context and outcomes within the project logs.

How does context preservation work when ending state management sessions?

Context preservation works by aggregating session data and refreshing the current state when the session ends. It updates content and session logs, ensuring the full conversation context is saved for future context retrieval.

Do I need a configured repository to save session logs and context?

You do not need a configured repository to save session logs and context, as the Skill aggregates session data and updates logs regardless. However, committing changes to git requires a configured VCS or repository.