memorix-git-memory

Search and inspect Git commit history to retrieve project memory.

618|48|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/AVIDS2/memorix --skill memorix-git-memory
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: memorix-git-memory
Source: https://github.com/AVIDS2/memorix/tree/main/plugins/copilot/memorix/skills/memorix-git-memory
Command: npx skills add https://github.com/AVIDS2/memorix --skill memorix-git-memory

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, and includes scripts (resource) components.

What problem does it solve?

This Skill provides a solution for managing and retrieving project memory based on Git commit history, making it easier to track changes, fixes, and engineering evidence.

Core Features & Use Cases

  • Commit History Analysis: Quickly search and inspect commit history for changes, fixes, and engineering evidence.
  • Memory Retrieval: Retrieve specific information from the Git-based memory system, such as what changed, when a fix was shipped, or which files were touched.
  • Use Case: When you need to reference past changes in a project or understand the context behind a specific commit, this Skill can help you access that information efficiently.

Quick Start

Use the memorix-git-memory skill to search for changes related to a specific feature branch.

Frequently Asked Questions about memorix-git-memory

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

FAQPage Schema
How do I search git commit history for specific changes and fixes?

Searching git commit history for changes and fixes requires tools that inspect and ingest commit data from your repository. This approach retrieves specific information such as what changed, when a fix shipped, and which files were touched.

What is git-based project memory and how does it work?

Git-based project memory is a system that manages and retrieves project context using Git commit history. It tracks changes, fixes, and engineering evidence by searching and inspecting commit data to provide historical context.

Can I retrieve engineering evidence from a specific feature branch in git?

Yes, you can retrieve engineering evidence from a specific feature branch in git. By searching the commit history associated with that branch, you can efficiently reference past changes and understand the context behind specific commits.

Do I need git installed to manage project memory from commit history?

Yes, you need git installed to manage project memory from commit history. Accessing repository history and metadata requires git and its associated command-line tools to search, inspect, and ingest commit data.

What's the best way to track when a fix was shipped using version control history?

The best way to track when a fix was shipped using version control history is to search and inspect git commit data. This retrieves specific information from the git-based memory system, including exact commit timestamps and affected files.

Why does retrieving project memory require command-line tools for git?

Retrieving project memory requires command-line tools for git because the system needs direct access to repository history and metadata. The scripts depend on git command-line utilities to search, inspect, and ingest the underlying commit data.