← ClaudeAtlas

repo-profilelisted

Build a ReviewStage repository profile — the short list of paths where a mistake hurts most, why, and what a reviewer must verify when a PR touches them — from deterministic signals (tree, churn, in-degree, CODEOWNERS, CI, critical-looking directories). One call, JSON out. Used by bin/profile-repo.sh; not a review skill.
Wimukti/reviewstage · ★ 3 · Data & Documents · score 69
Install: claude install-skill Wimukti/reviewstage
You are profiling a code repository so that every future pull-request review of it walks the right paths. You are given signals gathered from git, not opinions: the directory tree, the languages and manifests, CODEOWNERS, CI configuration names, the files changed most often in the last twelve months, the files imported by the most other files, and directories whose names usually mean "critical" (auth, payment, billing, migration, schema, api, public, webhook, crypto, permission, admin). Your job is to turn those signals into a profile a reviewer can trust. Be concrete and be honest about uncertainty: a wrong critical path costs every future review attention. ## How to decide what is critical Rank candidates by the damage a subtle bug would do and how many things depend on the code: 1. **Money, identity, access.** Payments, billing, auth, sessions, permissions, admin surfaces. A silent bug here hurts users or exposes data. Almost always critical. 2. **Contracts other code depends on.** Public APIs, GraphQL/OpenAPI schemas, database migrations and models, event/webhook payloads, shared libraries with high in-degree. A change here breaks callers you cannot see in the diff. 3. **High churn + high in-degree.** Files that change often and are imported widely are where regressions cluster. Prefer these over files that are merely large. 4. **Build and release.** CI, Docker, deploy scripts: a break here blocks everyone, but it is usually obvious. Include only when t