memory

Maintains persistent bot memory via a structured task ledger and decision log.

Updated Aug 26, 2026
One-click install
npx skills add https://github.com/rameshkumarchouhanr/gemni-cli --skill memory-rameshkumarchouhanr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: memory
Source: https://github.com/rameshkumarchouhanr/gemni-cli/tree/main/tools/gemini-cli-bot/.gemini/skills/memory
Command: npx skills add https://github.com/rameshkumarchouhanr/gemni-cli --skill memory-rameshkumarchouhanr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Long-running AI agents lose context between sessions, causing repeated investigations and forgotten decisions. This Skill standardizes how the Gemini CLI Bot persists state across sessions using a structured lessons-learned.md file. ## Core Features & Use Cases - Task Ledger Synchronization: Reads and updates a rolling ledger of the 50 most recent tasks, verifying PR and issue states via the GitHub CLI before starting work. - Decision & Hypothesis Logging: Records root-cause analyses, hypotheses, and architectural decisions in append-only logs with pruning rules to prevent context bloat. - Sub-agent State Delegation: Defines rules for passing ledger context to worker agents while restricting them to read-only memory access. - Use Case: A scheduled bot run begins by reading lessons-learned.md, marks merged PRs as DONE, investigates a failed task, then appends its findings and decisions before opening a new PR. ## Quick Start Activate the memory skill to synchronize the bot's task ledger with lessons-learned.md before starting the investigation and record all findings when finished.

Frequently Asked Questions about memory

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

FAQPage Schema
How do I give an AI agent persistent memory across sessions?

Store state in a structured Markdown file such as lessons-learned.md containing a task ledger, hypothesis ledger, and decision log. The agent reads this file at session start and updates it at session end to maintain continuity.

How to prevent AI agent memory files from growing too large?

Apply rolling-window pruning to the memory file. This Skill keeps only the 50 most recent tasks in the Task Ledger and the 20 most recent entries in the Decision Log, preventing context bloat over time.

Can sub-agents update the shared memory file directly?

No. Worker agents are strictly forbidden from writing to lessons-learned.md. They must return findings to the orchestrator, which remains the sole authority for state preservation and memory updates.

How does the bot verify task status before updating its ledger?

It uses the GitHub CLI commands gh pr view and gh issue view to check the current state of triggers, then marks merged PRs as DONE or investigates CI failures for FAILED tasks during scheduled runs.

What happens to pending tasks in interactive mode?

In interactive mode the bot ignores all FAILED, STUCK, or pending ledger tasks. Its only goal is addressing the specific user comment that triggered the session.