Skip to content
Skills Library
Programming · Analysis

clone-patterns

/clone-patterns

Learn From the Best — analyze patterns from any codebase and apply them to yours. Use when user wants to adopt best practices from another repo, compare code quality, or learn how top projects are structured.

Repository
ultraship ↗
Licence
MIT
Last repository change
08.07.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 08.07.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Learn From the Best — analyze patterns from any codebase and apply them to yours. Use when user wants to adopt best practices from another repo, compare code quality, or learn how top projects are structured.

Arguments

/clone-patterns <repo-url-or-path>
Original author description

Learn From the Best — analyze patterns from any codebase and apply them to yours. Use when user wants to adopt best practices from another repo, compare code quality, or learn how top projects are structured.

How it works

  1. Process
  2. Key Principle
Original SKILL.md headings · 95 lines, 355 words
SKILL.md preview
---
name: clone-patterns
description: "Learn From the Best — analyze patterns from any codebase and apply them to yours. Use when user wants to adopt best practices from another repo, compare code quality, or learn how top projects are structured."
argument-hint: "<repo-url-or-path>"
allowed-tools: Bash, Read, Grep, Glob
---

# Learn From the Best

Analyze any codebase's patterns and apply the best ones to your project.

## Process

### Phase 1: Analyze Source

Ask for the source project directory (must be cloned locally):
- "Which repo do you want to learn from? Provide the local path."

```bash
node ${CLAUDE_PLUGIN_ROOT}/tools/pattern-analyzer.mjs <source-directory> --compare=<your-project-directory>
```

Parse the JSON output.

### Phase 2: Pattern Report

Present the source project's patterns:

**Project Structure:**
- How they organize code (feature-based, layer-based, hybrid)
- Naming conventions
- Key directories

**Testing Strategy:**
- Framework and location
- Test-to-source ratio
- Integration vs unit separation

**Code Quality:**
- Average file length
- Export patterns
- Linting and formatting setup

**TypeScript Practices:**
- Strict mode usage
- Type vs interface preference
- `any` count

**Error Handling:**
- Custom error classes
- Middleware patterns
- Global handlers

**CI/CD:**
- Pipeline setup
- Automated steps

### Phase 3: Comparison

Show side-by-side comparison between the source project and yours:

For each area, show:
- What they do vs what you do
- Whether the difference matters
- Specific recommendation

### Phase 4: Adoption Plan

Create a prioritized adoption plan:

**Priority 1 (High Impact, Low Effort):**
- Enable TypeScript strict mode
- Add linting/formatting config
- Adopt naming conventions

**Priority 2 (High Impact, Medium Effort):**
- Add test framework and initial tests
- Create custom error classes
- Add CI pipeline

**Priority 3 (Medium Impact, Higher Effort):**
- Restructure project directories
- Add integration tests
- Improve documentation

### Phase 5: Apply Patterns

For each pattern the user wants to adopt, implement it:

1. **TypeScript strict mode** — update tsconfig.json, fix resulting errors
2. **Test framework** — install vitest/jest, create first test, add test script
3. **Error handling** — create base error class, add error middleware
4. **CI pipeline** — create .github/workflows/ci.yml with lint, test, build
5. **Linting** — add eslint config matching source project's style

Only apply patterns the user explicitly approves.

## Key Principle

**Steal like an artist.** The best codebases didn't invent their patterns — they borrowed from others and refined them. Learn what works, adapt it to your context, and make it your own.

Versions

The database has no other skills named clone-patterns.

Database snapshot: 13.11.2026 · package version 6d8499e56d81 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100coding-best-practices
    Reviews Swift/iOS code for adherence to modern Swift idioms, Apple platform best practices, architecture patterns, and code quality standards. Use when user mentions best practices, code review, clean code, refactoring, or wants to improve code quality.
  • 100code-review
    Reviews code for quality, best practices, and potential issues. Use when asked to review, audit, or check code for problems.
  • 100code-reviewer
    Use this agent when you need to conduct comprehensive code reviews focusing on code quality, security vulnerabilities, and best practices.
  • 100code-reviewer
    General-purpose code review skill. Provides checklists for security, code quality, performance, and best practices. Use when reviewing code changes, PRs, or performing quality audits.
  • 100best-practices
    Apply modern web development best practices for security, compatibility, and code quality. Use when asked to "apply best practices", "security audit", "modernize code", "code quality review", or "check for vulnerabilities".
  • 100customerio-sdk-patterns
    Apply production-ready Customer.io SDK patterns. Use when implementing best practices, refactoring integrations, or optimizing Customer.io usage in your application. Trigger with phrases like "customer.io best practices", "customer.io patterns", "production customer.io", "customer.io architecture".

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.