codex-session-learning

Convert past Codex debugging sessions into reusable prompts and validation rules.

19|2|Updated Mar 14, 2025

Search Tags:#debugging #codex #postmortem #prompt-engineering #validation-rules #case-library #knowledge-distillation

Ready to run

npx skills add https://github.com/ThalesGroup/agilab --skill codex-session-learning

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: codex-session-learning
Source: https://github.com/ThalesGroup/agilab/tree/main/.claude/skills/codex-session-learning
Command: npx skills add https://github.com/ThalesGroup/agilab --skill codex-session-learning

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Codex debugging sessions often produce scattered notes, patches, and memory-based guidance. This skill extracts the useful lessons into explicit, reusable assets including bug-fix guidance, prompts, and validation rules to speed up future debugging.

Core Features & Use Cases

Extract structured cases, reusable prompt patterns, and validation rules from prior Codex sessions.
Build postmortem catalogs and prompt-routing templates to guide future fixes.
Route bug logs into repeatable assets instead of relying on memory during iterative debugging across notebooks, scripts, and tools.

Quick Start

Convert a past Codex debugging session into a reusable prompt pack and validation assets for reuse in new runs.

Frequently Asked Questions about codex-session-learning

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

FAQPage Schema

How do I extract reusable prompt patterns from past debugging sessions?▼

You can extract reusable prompt patterns from past debugging sessions by converting scattered Codex traces into structured postmortems, prompt templates, and validation rules for future bug fixes.

What is knowledge distillation from Codex debugging traces?▼

Knowledge distillation from Codex debugging traces is the process of turning scattered session notes and patches into explicit, reusable bug-fix guidance, prompt templates, and validation rules.

How do I build a bug taxonomy and case library from prior debugging logs?▼

You build a bug taxonomy and case library by processing prior debugging logs to extract structured cases and postmortem catalogs, routing them into repeatable assets instead of relying on memory.

Can I generate validation rules from postmortem catalogs for future bug fixes?▼

Yes, you can generate validation rules from postmortem catalogs by extracting reusable guidance from prior Codex sessions and storing them in a durable destination like .tokki/rules in your repo.

Does this approach work for debugging across notebooks, scripts, and tool runs?▼

Yes, this approach works for iterative debugging across notebooks, scripts, and tool runs by routing bug logs into repeatable assets and prompt-routing templates to guide future fixes.