Repo Scanner
Scans any repository to build a complete picture of the current technical setup and scores production readiness.
How It Works
- Read the root directory tree to identify project type and structure
- Detect the tech stack from config files
- Check for production infrastructure (CI/CD, Docker, hosting)
- Check for observability (monitoring, error tracking, logging)
- Check for developer experience (documentation, agent config, tooling)
- Output a structured scan report using the EXACT format below
Step-by-Step Procedure
Step 1: Read Directory Structure
find . -type f -not -path './.git/*' -not -path './node_modules/*' -not -path './.next/*' -not -path './dist/*' -not -path './__pycache__/*' -not -path './venv/*' | head -200
Step 2: Detect Tech Stack
Check for these files to determine the stack:
| File |
Stack |
package.json |
Node.js / JavaScript / TypeScript |
tsconfig.json |
TypeScript |
next.config.* |
Next.js |
vite.config.* |
Vite |
requirements.txt / pyproject.toml |
Python |
go.mod |
Go |
Cargo.toml |
Rust |
Gemfile |
Ruby |
Read package.json or equivalent to understand dependencies and scripts.
Step 3: Check Production Infrastructure
| Check |
How |
| CI/CD |
Look for .github/workflows/, .gitlab-ci.yml, Jenkinsfile |
| Docker |
Look for Dockerfile, docker-compose.yml, .dockerignore |
| Hosting |
Look for vercel.json, railway.toml, fly.toml, render.yaml, serverless.yml |
| Environments |
Look for .env.example, .env.local, .env.production |
| Build |
Check for build scripts in package.json or Makefile |
Step 4: Check Observability
| Check |
How |
| Error tracking |
Grep for sentry, @sentry/, posthog, datadog, bugsnag in deps or code |
| Analytics |
Grep for gtag, analytics, mixpanel, amplitude |
| Logging |
Check for structured logging (winston, pino, structlog, loguru) |
| Health checks |
Look for /health, /healthz, /api/health endpoints |
Step 5: Check Developer Experience
| Check |
How |
| Root README |
Does README.md exist with setup instructions? |
| Directory READMEs |
`find . -name "README.md" -not -path './node_modules/*' |
| Agent config |
Look for AGENTS.md, .cursorrules, .cursor/rules/, .claude/ |
| Linting |
Look for .eslintrc, .prettierrc, ruff.toml |
| Testing |
Look for __tests__/, tests/, spec/, test scripts |
| Git hygiene |
Check .gitignore exists and covers common patterns |
Step 6: Check Security
Return filenames only from credential detection. Never print matching source lines or values; verify candidates with redaction before declaring a leak.
grep -rl "sk-\|api_key\s*=\s*['\"].\+['\"]" --include="*.ts" --include="*.js" --include="*.py" --include="*.env" . 2>/dev/null | grep -v node_modules | grep -v '.env.example' | head -20
MANDATORY Output Format
You MUST use this exact markdown structure. Do not invent your own format.
## 🔍 Repo Scan: {project-name}
**Tech Stack:** {e.g. React 18 + TypeScript, Flask + Python 3.11}
**Hosting:** {e.g. Vercel, AWS, Railway, or "Not configured"}
**Framework:** {e.g. Next.js 14, Vite 5, FastAPI}
---
## 📊 Production Readiness Score: {X}/10
| # | Category | Status | Details |
|---|----------|--------|---------|
| 1 | Environment Setup | {✅/⚠️/❌} | {one-line detail} |
| 2 | CI/CD Pipeline | {✅/⚠️/❌} | {one-line detail} |
| 3 | Documentation | {✅/⚠️/❌} | {one-line detail} |
| 4 | Error Tracking | {✅/⚠️/❌} | {one-line detail} |
| 5 | Deployment | {✅/⚠️/❌} | {one-line detail} |
| 6 | Security | {✅/⚠️/❌} | {one-line detail} |
| 7 | Cost Awareness | {✅/⚠️/❌} | {one-line detail} |
| 8 | Integration Health | {✅/⚠️/❌} | {one-line detail} |
| 9 | LLM-Readiness | {✅/⚠️/❌} | {one-line detail} |
| 10 | Code Organization | {✅/⚠️/❌} | {one-line detail} |
**Scoring: ✅ = 1 point, ⚠️ = 0.5 points, ❌ = 0 points**
---
## 🚨 Top 3 Issues
1. **{Issue title}** — {Why it matters. File:line reference if applicable.}
2. **{Issue title}** — {Why it matters.}
3. **{Issue title}** — {Why it matters.}
---
## 🛠️ Recommended Next Steps
Run these skills to fix the issues above:
1. `{skill-name}` — {what it will fix}
2. `{skill-name}` — {what it will fix}
3. `{skill-name}` — {what it will fix}
Rules for the output:
- Use the EXACT table format above with ✅/⚠️/❌ status icons
- Score is X/10 where ✅=1, ⚠️=0.5, ❌=0
- Top 3 issues must include specific file:line references when possible
- Recommended next steps must name real skills from this set:
deployment-engineer (CI/CD, Docker, environments), deploy-to-vercel or railway (hosting), monitoring-setup (errors, analytics, health), security-auditor (secrets, deps, auth), cloud-cost-optimizer (cloud spend), dev-tool-integrations (Slack/Linear/Sentry wiring), agents-md-writer (AGENTS.md / LLM-readiness), repo-structurer (READMEs, dead code, modularity)
- Keep the entire output under 100 lines
- Do NOT add extra sections, executive summaries, or risk assessments
1---2name: repo-readiness-scan3description: >-4 Scores a repository's production readiness out of 10 across stack, hosting, CI/CD, environments,5 error tracking, docs, security, cost, integrations, LLM-readiness and code organisation, with6 the top 3 issues and which skills fix them. Use when the user asks how production-ready their7 repo is, wants a readiness score or repo scan, or asks what to fix first before launch. Not for8 a deep security review (use security-auditor).9metadata:10 source: https://skillmd.com/skills/the-utopia-studio/repo-readiness-scan11---1213# Repo Scanner1415Scans any repository to build a complete picture of the current technical setup and scores production readiness.1617## How It Works18191. Read the root directory tree to identify project type and structure202. Detect the tech stack from config files213. Check for production infrastructure (CI/CD, Docker, hosting)224. Check for observability (monitoring, error tracking, logging)235. Check for developer experience (documentation, agent config, tooling)246. Output a structured scan report using the EXACT format below2526## Step-by-Step Procedure2728### Step 1: Read Directory Structure29```bash30find . -type f -not -path './.git/*' -not -path './node_modules/*' -not -path './.next/*' -not -path './dist/*' -not -path './__pycache__/*' -not -path './venv/*' | head -20031```3233### Step 2: Detect Tech Stack3435Check for these files to determine the stack:3637| File | Stack |38|------|-------|39| `package.json` | Node.js / JavaScript / TypeScript |40| `tsconfig.json` | TypeScript |41| `next.config.*` | Next.js |42| `vite.config.*` | Vite |43| `requirements.txt` / `pyproject.toml` | Python |44| `go.mod` | Go |45| `Cargo.toml` | Rust |46| `Gemfile` | Ruby |4748Read `package.json` or equivalent to understand dependencies and scripts.4950### Step 3: Check Production Infrastructure5152| Check | How |53|-------|-----|54| **CI/CD** | Look for `.github/workflows/`, `.gitlab-ci.yml`, `Jenkinsfile` |55| **Docker** | Look for `Dockerfile`, `docker-compose.yml`, `.dockerignore` |56| **Hosting** | Look for `vercel.json`, `railway.toml`, `fly.toml`, `render.yaml`, `serverless.yml` |57| **Environments** | Look for `.env.example`, `.env.local`, `.env.production` |58| **Build** | Check for build scripts in `package.json` or `Makefile` |5960### Step 4: Check Observability6162| Check | How |63|-------|-----|64| **Error tracking** | Grep for `sentry`, `@sentry/`, `posthog`, `datadog`, `bugsnag` in deps or code |65| **Analytics** | Grep for `gtag`, `analytics`, `mixpanel`, `amplitude` |66| **Logging** | Check for structured logging (winston, pino, structlog, loguru) |67| **Health checks** | Look for `/health`, `/healthz`, `/api/health` endpoints |6869### Step 5: Check Developer Experience7071| Check | How |72|-------|-----|73| **Root README** | Does `README.md` exist with setup instructions? |74| **Directory READMEs** | `find . -name "README.md" -not -path './node_modules/*' | wc -l` |75| **Agent config** | Look for `AGENTS.md`, `.cursorrules`, `.cursor/rules/`, `.claude/` |76| **Linting** | Look for `.eslintrc`, `.prettierrc`, `ruff.toml` |77| **Testing** | Look for `__tests__/`, `tests/`, `spec/`, test scripts |78| **Git hygiene** | Check `.gitignore` exists and covers common patterns |7980### Step 6: Check Security8182Return filenames only from credential detection. Never print matching source lines or values; verify candidates with redaction before declaring a leak.83```bash84grep -rl "sk-\|api_key\s*=\s*['\"].\+['\"]" --include="*.ts" --include="*.js" --include="*.py" --include="*.env" . 2>/dev/null | grep -v node_modules | grep -v '.env.example' | head -2085```8687## MANDATORY Output Format8889**You MUST use this exact markdown structure. Do not invent your own format.**9091````markdown92## 🔍 Repo Scan: {project-name}9394**Tech Stack:** {e.g. React 18 + TypeScript, Flask + Python 3.11}95**Hosting:** {e.g. Vercel, AWS, Railway, or "Not configured"}96**Framework:** {e.g. Next.js 14, Vite 5, FastAPI}9798---99100## 📊 Production Readiness Score: {X}/10101102| # | Category | Status | Details |103|---|----------|--------|---------|104| 1 | Environment Setup | {✅/⚠️/❌} | {one-line detail} |105| 2 | CI/CD Pipeline | {✅/⚠️/❌} | {one-line detail} |106| 3 | Documentation | {✅/⚠️/❌} | {one-line detail} |107| 4 | Error Tracking | {✅/⚠️/❌} | {one-line detail} |108| 5 | Deployment | {✅/⚠️/❌} | {one-line detail} |109| 6 | Security | {✅/⚠️/❌} | {one-line detail} |110| 7 | Cost Awareness | {✅/⚠️/❌} | {one-line detail} |111| 8 | Integration Health | {✅/⚠️/❌} | {one-line detail} |112| 9 | LLM-Readiness | {✅/⚠️/❌} | {one-line detail} |113| 10 | Code Organization | {✅/⚠️/❌} | {one-line detail} |114115**Scoring: ✅ = 1 point, ⚠️ = 0.5 points, ❌ = 0 points**116117---118119## 🚨 Top 3 Issues1201211. **{Issue title}** — {Why it matters. File:line reference if applicable.}1222. **{Issue title}** — {Why it matters.}1233. **{Issue title}** — {Why it matters.}124125---126127## 🛠️ Recommended Next Steps128129Run these skills to fix the issues above:1301311. `{skill-name}` — {what it will fix}1322. `{skill-name}` — {what it will fix}1333. `{skill-name}` — {what it will fix}134````135136**Rules for the output:**137- Use the EXACT table format above with ✅/⚠️/❌ status icons138- Score is X/10 where ✅=1, ⚠️=0.5, ❌=0139- Top 3 issues must include specific file:line references when possible140- Recommended next steps must name real skills from this set: `deployment-engineer` (CI/CD, Docker, environments), `deploy-to-vercel` or `railway` (hosting), `monitoring-setup` (errors, analytics, health), `security-auditor` (secrets, deps, auth), `cloud-cost-optimizer` (cloud spend), `dev-tool-integrations` (Slack/Linear/Sentry wiring), `agents-md-writer` (AGENTS.md / LLM-readiness), `repo-structurer` (READMEs, dead code, modularity)141- Keep the entire output under 100 lines142- Do NOT add extra sections, executive summaries, or risk assessments