pattern-extractor

Extract coding patterns from scan-report.json into structured patterns.json.

Updated Jan 23, 2026
One-click install
npx skills add https://github.com/datorresb/vibecoding-starter --skill pattern-extractor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pattern-extractor
Source: https://github.com/datorresb/vibecoding-starter/tree/main/.claude/skills/assimilation/pattern-extractor
Command: npx skills add https://github.com/datorresb/vibecoding-starter --skill pattern-extractor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill analyzes a codebase to identify recurring patterns, coding conventions, and architectural decisions, enabling consistent pattern discovery and guidance for skill generation.

Core Features & Use Cases

  • Deep pattern discovery: Extract architecture, reliability, quality, and conventions patterns from repository source.
  • Pattern output generation: Produce a structured patterns.json suitable for assimilation pipelines and downstream tooling.
  • Use Case: Prepare architectural decision records by summarizing common patterns across a large codebase for technical leadership reviews.

Quick Start

Run the assimilation workflow on your project to generate .github/temp/patterns.json from the scan results in .github/temp/scan-report.json.

Frequently Asked Questions about pattern-extractor

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

FAQPage Schema
How do I extract architecture patterns from a source code repository?

To extract architecture patterns from a repository, you analyze the source code's scan-report.json to identify reliability, quality, and convention patterns, outputting a structured patterns.json file for downstream assimilation.

What are coding conventions and how do I discover them in my codebase?

Coding conventions are recurring patterns and architectural decisions in source code. You discover them by analyzing a repository scan report to identify and summarize reliability, quality, and architecture patterns into a structured JSON format.

How do I generate a patterns.json file for a downstream assimilation pipeline?

Generate a patterns.json file by running an assimilation workflow on your project, which reads the repository scan results from .github/temp/scan-report.json and extracts structured coding patterns into .github/temp/patterns.json.

Do I need a scan-report.json file before extracting code patterns?

Yes, extracting code patterns requires a pre-existing scan-report.json file, typically generated by a repo-scanner tool in the .github/temp/ directory, to analyze and identify architectural decisions and coding conventions.

Can I summarize codebase patterns for architectural decision records?

Yes, you can summarize codebase patterns for architectural decision records by extracting architecture, reliability, and quality patterns from your repository source code into a structured format for technical leadership reviews.

What is the best way to prepare a large codebase for pattern discovery?

The best way to prepare a large codebase for pattern discovery is running a repository scanner to generate a scan-report.json, then extracting architecture and convention patterns into a structured patterns.json output for consistent analysis.