michaelboeding/skills

Overview

This skill analyzes a codebase to extract its conventions, patterns, and style. It spawns specialized analyzer agents that each focus on one aspect and synthesizes their findings into a single, machine-readable style guide. Use it to make implicit conventions explicit and to align future work with existing code patterns.

How this skill works

The skill first detects the primary language and frameworks, then spawns five analyzers in parallel (structure, naming, patterns, testing, frontend). Each analyzer explores the repo using file listing and search, extracts concrete examples from existing files, and returns a structured report. The reports are merged into a unified style guide file saved under .claude/codebase-style.md and a short summary is presented to the user.

When to use it

• Starting work on an unfamiliar codebase
• Onboarding contributors who need to follow existing conventions
• Before implementing features so code matches current patterns
• When implicit conventions should be documented explicitly
• After significant refactors or framework upgrades

Best practices

• Run a language/framework detection pass before deep analysis
• Spawn all analyzers in parallel to save time and surface conflicts
• Extract examples from real files—document observed patterns, not opinions
• Record conflicts explicitly and include both variants when unsure
• Regenerate the guide after major structural or dependency changes

Example use cases

• Generate a project style guide to feed other automation agents for consistent code generation
• Confirm naming conventions (files, classes, functions) before a large merge
• Detect testing patterns and suggest where new tests should live
• Identify frontend component and styling patterns before adding UI features
• Create a reference that code reviewers and CI checks can consult