Agent Skills › Houseofmvps/ultraship › clone-patterns

clone-patterns

GitHub

分析任意代码库的最佳实践模式，对比当前项目，生成采纳计划并协助实施，帮助开发者学习优秀架构与规范。

skills/clone-patterns/SKILL.md Houseofmvps/ultraship

Trigger Scenarios

用户希望借鉴其他仓库的最佳实践用户想要比较代码质量或结构差异用户需要制定代码重构或规范升级计划

Install

npx skills add Houseofmvps/ultraship --skill clone-patterns -g -y

More Options

Use without installing

npx skills use Houseofmvps/ultraship@clone-patterns

指定 Agent (Claude Code)

npx skills add Houseofmvps/ultraship --skill clone-patterns -a claude-code -g -y

安装 repo 全部 skill

npx skills add Houseofmvps/ultraship --all -g -y

预览 repo 内 skill

npx skills add Houseofmvps/ultraship --list

SKILL.md

Frontmatter

{
    "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.",
    "allowed-tools": "Bash, Read, Grep, Glob",
    "argument-hint": "<repo-url-or-path>"
}

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."

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:

TypeScript strict mode — update tsconfig.json, fix resulting errors
Test framework — install vitest/jest, create first test, add test script
Error handling — create base error class, add error middleware
CI pipeline — create .github/workflows/ci.yml with lint, test, build
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.