sloth-commit

Automate commit and push of Claude Code memory changes to a private GitHub repository.

1|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/coreymaypray/sloth-skill-tree --skill sloth-commit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sloth-commit
Source: https://github.com/coreymaypray/sloth-skill-tree/tree/main/plugins/maycrest-ops/skills/sloth-commit
Command: npx skills add https://github.com/coreymaypray/sloth-skill-tree --skill sloth-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the process of recording, committing, and pushing Claude Code memory changes to a private GitHub repository, ensuring memory state is versioned and auditable.

Core Features & Use Cases

  • Auto-commit: detects changes in the Claude Code memory directory and creates a descriptive commit message.
  • Push synchronization: pushes commits to the private claude-code-memory repository to keep memory references in sync.
  • Safe workflow: includes steps to review changes before committing and maintains a clean memory history.

Quick Start

Commit and push all Claude Code memory changes from the designated memory directory to the private claude-code-memory GitHub repository.

Frequently Asked Questions about sloth-commit

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

FAQPage Schema
How do I automatically commit Claude Code memory changes to GitHub?

You can automate Claude Code memory commits by using this skill to stage memory directory changes, generate descriptive commit messages, and push them to a private GitHub repository.

What is the best way to keep Claude Code memory versioned and auditable?

Versioning Claude Code memory involves pushing memory state changes to a private GitHub repository, ensuring local and remote references stay synchronized with a descriptive commit history.

Do I need a private GitHub repository to sync Claude Code memory?

Yes, a private claude-code-memory GitHub repository is required to safely store, version, and audit your Claude Code memory state across local and remote environments.

Can I review Claude Code memory changes before pushing to the remote repository?

Yes, the automated memory commit workflow includes steps to review changes before committing, maintaining a clean memory history while pushing updates safely to the remote repository.

Does sloth-commit work with standard git automation workflows for memory management?

sloth-commit applies standard git automation to memory management by detecting changes in the Claude Code memory directory, creating descriptive commits, and pushing them to sync local and remote state.

Why does my Claude Code memory state get out of sync between local and remote storage?

Claude Code memory state gets out of sync when local changes lack an automated commit and push workflow to version the memory directory and update the remote GitHub repository.