corgispec-memory-extract

Extract patterns and write session summaries from completed AI coding changes.

113|9|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/ricoyudog/Coding_Corgi_flow --skill corgispec-memory-extract
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: corgispec-memory-extract
Source: https://github.com/ricoyudog/Coding_Corgi_flow/tree/main/.opencode/skills/atoms/corgispec-memory-extract
Command: npx skills add https://github.com/ricoyudog/Coding_Corgi_flow --skill corgispec-memory-extract

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converting completed AI coding work into durable, organization-wide knowledge—so future changes can reuse proven approaches instead of repeating the same discoveries and decisions.

Core Features & Use Cases

  • Pattern extraction to long-term wiki memory: Creates reusable pattern pages under wiki/patterns/ based on non-trivial, repeatable approaches found in the completed change.
  • Session summaries for historical traceability: Writes wiki/sessions/<change-name>.md capturing timeline, key decisions, pitfalls, and outcomes (without overwriting existing summaries).
  • Lifecycle bookkeeping across artifacts: Moves the change from wiki/hot.md Active to Recently Shipped, resets memory/session-bridge.md for the archived change, and updates wiki/index.md plus relevant _index.md files with new links.

Quick Start

Use corgispec-memory-extract to archive a finished change named "my-change" and automatically generate any patterns and a session summary in the wiki.

Frequently Asked Questions about corgispec-memory-extract

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

FAQPage Schema
How do I extract reusable patterns from completed AI coding sessions?

To extract reusable patterns from completed AI coding sessions, you distill non-trivial approaches from finished changes into long-term wiki memory. This creates reusable pattern pages under the wiki/patterns directory for future reference.

What is the best way to write a session summary for a completed change before archiving?

Writing a session summary for a completed change involves capturing the timeline, key decisions, pitfalls, and outcomes into a historical traceability file. This ensures the wiki sessions record is preserved without overwriting existing summaries.

How does cross-session context lifecycle bookkeeping work when finalizing a change?

Cross-session context lifecycle bookkeeping updates wiki index pages and moves the change from Active to Recently Shipped. It resets the session-bridge memory for the archived change while keeping other active change entries intact.

Do I need full archive closure to extract knowledge distillation from a finished task?

You do not need full archive closure to perform knowledge distillation from a finished task. Pattern extraction and session summary generation can be applied when knowledge extraction is needed independently of the final archiving step.

Can I clear individual archived entries in the session bridge without affecting active changes?

You can clear individual archived entries in the session bridge without affecting active changes. The knowledge extraction process selectively clears only the archived change entries in memory, leaving all other ongoing work intact.