← ClaudeAtlas

repo-estimatorlisted

Analyze a code repository and produce a detailed human time and cost estimate for building it from scratch. Use this skill whenever the user wants to know how long it would take a human developer or team to build a codebase, how much it would cost to recreate a project, what the engineering effort of a repo is, or wants a "what's this worth?" / "how much work went into this?" type of analysis. Also trigger for requests like "estimate this project", "how many dev hours is this", "what would it cost to build this", "audit this repo for effort", "scope this codebase", or any time someone shares a repo path or GitHub URL and asks about effort, time, team size, or cost. Even if they don't use the words "estimate" or "cost" — if they share code and ask about effort or what it would take to build, use this skill.
teterouge/codeworth · ★ 0 · AI & Automation · score 47
Install: claude install-skill teterouge/codeworth
# Repo Estimator This skill produces a thorough, defensible estimate of the human time and cost required to build a codebase from scratch. It's designed for founders evaluating acquisitions, engineers scoping migrations, freelancers pricing projects, or anyone who wants to understand the real effort baked into a repository. The output should feel like something a senior engineering consultant would hand over — not a naive line-count calculation, but a judgment-call-rich analysis that accounts for complexity, architecture, rework cycles, and team dynamics. ## What You're Estimating You're answering: **"If a competent team started from zero today, how long would it take and what would it cost to build what's in this repo?"** This is subtly different from: - "How long did it take the original team?" (You don't know their pace, mistakes, or false starts) - "How many lines of code are there?" (LOC is a famously poor proxy for effort) - "What's the maintenance cost?" (That's a different question — don't conflate it unless asked) Assume the hypothetical team is **competent but unfamiliar with the domain**. They need to design, build, test, and document — not just type. --- ## Step 1: Understand the Request Before diving in, understand what the user actually needs: - **Target**: Is this a local path, a GitHub URL, or a zip? Handle accordingly. - **Purpose**: Are they buying/selling, scoping a rewrite, hiring, or just curious? This shapes how you frame the output. - **Team a