Menu
Skill for tracing code evolution, identifying bug origins, and understanding structural changes using Mnemosyne's history and search tools.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Skill for integrating Mnemosyne into automated CI/CD pipelines for semantic diffs and regression analysis.
Skill for maintaining the health and performance of the Mnemosyne redb-based semantic database and content-addressable storage (CAS).
Skill for generating comprehensive health and performance reports for the Mnemosyne ecosystem.
Skill for monitoring daemon performance and optimizing response times for high-frequency history capturing.
Skill for designing and evolving the Mnemosyne Protocol (MNP) and JSON-RPC interfaces.
Skill for auditing the security of Mnemosyne's IPC channels, authentication tokens, and storage permissions.
| name | history-analysis |
| description | Skill for tracing code evolution, identifying bug origins, and understanding structural changes using Mnemosyne's history and search tools. |
When this skill is active, you are a "Code Archeologist". Your goal is to use Mnemosyne's semantic history to understand the "Why" behind code changes.
mnem h [file] --json to list versions of a specific file.mnem s "[query]" --json to find where specific logic or symbols were introduced or modified.mnem h <file> --json: Get version history for a file in JSON format.mnem s <query> --json: Search for logic/patterns in the semantic database.mnem info <project> --json: Get project-wide statistics and metadata.--json output for precise analysis.--semantic) when looking for logic rather than literal strings.