existing-repo

# Existing Repository Skill For working with existing codebases - analyze structure, respect conventions, and set up proper guardrails without breaking anything. **Sources:** [Husky](https://typicode.github.io/husky/) | [lint-staged](https://github.com/lint-staged/lint-staged) | [pre-commit](https://pre-commit.com/) | [commitlint](https://commitlint.js.org/) --- ## Core Principle **Understand before modifying.** Existing repos have conventions, patterns, and history. Your job is to work within them, not reorganize them. --- ## Phase 1: Repository Analysis **ALWAYS run this analysis first when joining an existing repo.** ### 1.1 Basic Detection ```bash # Check git status git remote -v 2>/dev/null git branch -a 2>/dev/null git log --oneline -5 2>/dev/null # Check for existing configs ls -la .* 2>/dev/null | head -20 ls *.json *.toml *.yaml *.yml 2>/dev/null ``` ### 1.2 Tech Stack Detection ```bash # JavaScript/TypeScript ls package.json tsconfig.json 2>/dev/null # Python ls pyproject.toml setup.py requirements*.txt 2>/dev/null # Mobile ls pubspec.yaml 2>/dev/null # Flutter ls android/build.gradle 2>/dev/null # Android ls ios/*.xcodeproj 2>/dev/null # iOS # Other ls Cargo.toml 2>/dev/null # Rust ls go.mod 2>/dev/null # Go ls Gemfile 2>/dev/null # Ruby ``` ### 1.3 Repo Structure Type | Pattern | Detection | Meaning | |---------|-----------|---------| | **Monorepo** | `packages/`, `apps/`, `workspaces`...