patterns

Generate a PATTERNS manifest from a codebase's observed conventions.

Updated May 4, 2026
One-click install
npx skills add https://github.com/olioskar/comb-the-desert-claude-plugin --skill patterns-olioskar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: patterns
Source: https://github.com/olioskar/comb-the-desert-claude-plugin/tree/main/skills/patterns
Command: npx skills add https://github.com/olioskar/comb-the-desert-claude-plugin --skill patterns-olioskar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns a codebase into a reliable convention map, so teams can quickly understand how the project actually structures code, names things, handles errors, and tests behavior.

Core Features & Use Cases

  • Observed baseline generation: Scans the repository and records concrete conventions with real file references instead of guessing from policy text.
  • Project-specific manifest: Produces or refreshes a PATTERNS manifest that downstream review and implementation workflows can use as shared context.
  • Use case: When a project starts drifting or a new contributor needs orientation, this Skill captures the current norms for structure, vocabulary, reuse points, and testing practice in one place.

Quick Start

Use the patterns skill to scan the repository and generate or refresh the PATTERNS manifest for the current project.

Frequently Asked Questions about patterns

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

FAQPage Schema
How do I extract coding conventions from an existing codebase for new contributors?

A codebase convention map records a project's observed norms for structure, naming, reuse, and testing using real file references. It captures how the project actually handles code, rather than guessing from policy text, to provide a reliable shared context.

How do I generate a project conventions manifest for code review workflows?

Generate a conventions manifest by scanning the repository tree and real file references to produce a PATTERNS file. This directive-aware record captures structural and testing baselines, serving as shared context for downstream code review and implementation workflows.

Can I capture structural and naming patterns without configuring external dependencies?

Yes, you can capture structural and naming patterns without external dependencies. The Skill requires only the repository tree and real file references to produce a directive-aware, human-reviewable convention record.

What's the best way to document actual error-handling and testing practices in a repository?

Document actual error-handling and testing practices by observing real file references during a repository scan. This generates a PATTERNS manifest that records concrete, observed conventions instead of relying on idealized policy text.

When do I need to refresh a project's PATTERNS manifest?

Refresh a PATTERNS manifest when a project starts drifting from its established norms or when structural, naming, and testing conventions evolve. It captures current observed baselines to maintain accurate context for implementation workflows.