skill-master_skill

Overview

This skill analyzes a codebase to discover architectural and implementation patterns and auto-generates or syncs skill files under .claude/skills/. It supports multi-platform projects and produces versioned, source-linked skill documents with real, anonymized examples. Use it to find gaps, create new skill artifacts from code patterns, or keep existing skill files aligned with project structure.

How this skill works

It scans the repository to detect platform indicators (build files, package manifests) and searches source roots for pattern signatures such as ViewModel, Repository, or service interfaces. The skill compares discovered patterns against existing .claude/skills/ entries, selects representative source files, extracts structure and conventions, and generates or updates skill files with code examples and rule sets. For updates it preserves custom content, applies a deterministic merge strategy, and records sources and version changes in a marker at the file end.

When to use it

• When you suspect missing skill files for common architectural patterns
• When you want to bootstrap skill documents from an existing codebase
• When syncing skill files after refactor or platform changes
• When you need quick, example-based documentation of patterns found in source
• When auditing a multi-platform repo for pattern coverage

Best practices

• Run discovery first to get a gap analysis before generating files
• Keep source roots and build files committed so platform detection works reliably
• Provide .ruler/*.md rules if you want custom Do/Don't guidance extracted
• Review generated examples to anonymize business logic before publishing
• Rely on backups created on first-run to preserve any pre-existing custom content

Example use cases

• Generate a Repository/ViewModel skill for an Android module by scanning build.gradle and Kotlin sources
• Detect React component patterns and create a react-web skill with representative JSX examples
• Sync skills after migrating services to a new package layout so markers and versions reflect changes
• Extract rules from .ruler/ files and include them as Do/Don't sections in generated skills
• Produce a report listing detected patterns, existing skills, and missing skill candidates for team review