commit-moonshot

To automate git commits for project memory, this skill analyzes repository changes, updates memory entities and boundaries via the Memory MCP, and executes a standardized commit with an auditable message.

Project memory in version-control workflows is a tracked state of impacted components, domains, and APIs. This skill updates these memory entities and relationships to reflect the current repository state before committing.

You maintain an audit trail for memory updates by enforcing a stepwise memory update procedure and generating compliant commit messages. This skill standardizes that process for main-session software workflows.

Yes, you need jq and package.json to use this skill. It relies on jq for processing memory updates and extracts the project ID from package.json to maintain boundaries and domains during the commit process.

Yes, you can use this skill to analyze repository changes. It identifies impacted components and APIs, updates memory boundaries and relationships, and commits those updates to the global Memory MCP.

You should not use an automated memory commit workflow for projects lacking a package.json or git repository. This skill requires both to extract project IDs, maintain memory boundaries, and execute standardized version-control commits.