skills.rest
jonathanmalkin
jonathanmalkinCOMMUNITY
Explore all skills by this author →
GitHub

retro-deep

Analyzes a chat session and automatically applies fixes to prevent recurrence.

61|9|Updated Mar 9, 2026
Search Tags:#debugging#self-improvement#compliance#retrospective#auditing#session analysis
One-click install
npx skills add https://github.com/jonathanmalkin/jules --skill retro-deep
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro-deep
Source: https://github.com/jonathanmalkin/jules/tree/main/.claude/skills/retro-deep
Command: npx skills add https://github.com/jonathanmalkin/jules --skill retro-deep

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill performs a comprehensive audit of a conversation session to identify issues, compliance failures, and areas for improvement, automatically applying fixes to prevent recurrence.

Core Features & Use Cases

  • Issue Identification: Detects repeated errors, compliance gaps, missing guidance, workarounds, and knowledge gaps.
  • Automated Fixes: Updates memory, rules, skills, or CLAUDE.md based on identified issues.
  • Pattern Detection: Identifies cross-session recurring problems.
  • Use Case: After a complex or problematic coding session, run this Skill to get a detailed report of what went wrong, why, and have the system automatically adjust its configuration to avoid similar issues in the future.

Quick Start

Run a deep retrospective of the current session.

Frequently Asked Questions about retro-deep

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

FAQPage Schema
How do I audit a coding session to find compliance failures and workarounds?▼

Conducting a deep retrospective analysis audits a coding session by detecting compliance failures, missing guidance, and workarounds. It categorizes these issues and cross-references them against existing configurations to pinpoint root causes.

Can I automatically apply fixes to memory and rules after a problematic coding session?▼

Yes, automated fixes can be applied directly to memory, rules, skills, or CLAUDE.md configurations after a session. This updates the system to prevent the recurrence of identified workarounds and compliance gaps.

What is session forensics for software engineering conversations?▼

Session forensics is the deep retrospective analysis of a conversation to identify compliance failures, missing guidance, and knowledge gaps. It researches solutions and generates a detailed report of what went wrong and why.

How do I detect recurring cross-session issues and repeated errors?▼

You detect recurring cross-session issues by running a deep retrospective that identifies repeated errors and pattern detection. This analyzes conversation histories to find ongoing problems and missing guidance.

Does session retrospective analysis identify determinism candidates for scripting?▼

Yes, session retrospective analysis identifies determinism candidates for scripting during the audit. It highlights repetitive conversational tasks that can be converted into automated scripts to prevent future manual workarounds.

Related Skills

Explore More Software Engineering Skills→
phrazzldphrazzld
13

done

Analyze git diffs and logs to codify session learnings into actionable artifacts.

Community
Advanced
treesus6treesus6
1

continuous-learning-v2

Automate rule and skill generation from React Native development patterns.

Community
Advanced
khairulariffinkakhairulariffinka
1

orchestration

Coordinate multiple AI agents across planning, execution, validation, and recovery workflows.

Community
Advanced
MinhDuyDEVMinhDuyDEV

root-cause-tracing

Traces software failures backward through execution paths to identify their original source.

Community
Advanced