extract-patterns

To document reusable code patterns, scan your codebase to find recurring abstractions and architectural approaches, then generate detailed markdown files and a concise index for project-wide agent reference.

The best way to extract recurring code structures is running an automated scan of completed features to identify abstractions, generate markdown documentation, and commit the pattern updates directly into your pipeline.

Pattern discovery prevents architectural drift by using glob and grep tools to scan repository files, identifying proven utilities and structures, and creating a dense index that agents reference for future development.

You should generate pattern files after completing a major feature, encountering recurring structures, or starting a new project phase to capture proven architectural approaches and prevent duplicated effort.

Yes, you can automate code analysis without external dependencies by using built-in read, write, glob, grep, and task tools to scan files, generate markdown documentation, and commit changes directly.

Automated pattern extraction works for large codebases by scanning completed features and recurring structures to generate markdown documentation, capturing existing patterns to realign project consistency moving forward.