pattern-extractor

You can detect recurring patterns and anti-patterns from iteration history by running the pattern-extractor to analyze project iteration logs and error records, automatically extracting confirmed patterns for code improvement.

Yes, you can generate reusable skills from error logs by analyzing iteration history to extract confirmed best practices, which are then automatically converted into reusable skill candidates.

You should run pattern detection on your iteration logs every 5 iterations or at session end to automatically update your pattern catalog and skill set with the latest recurring practices.

Automated pattern extraction requires access to your project's iteration logs and error records to analyze recurring patterns, anti-patterns, and best practices for skill generation.

Yes, pattern extraction works without external dependencies, requiring only your project's iteration logs and error records to analyze iteration history and generate reusable skills.

Pattern detection analyzes iteration history and error logs to extract recurring patterns, while skill generation converts those confirmed patterns into reusable skills for future code improvement.