repo-reliability

name	repo-reliability
description	Analyze a git repository's development-process health and fragility — commit patterns, code churn, contributor concentration, PR flow vs review depth, issue responsiveness — via extensible per-pointer scripts that emit JSON envelopes, aggregated into a persistent multi-project dashboard on mosaic. Use when asked to assess a repo's reliability, maturity, commit/PR patterns, or how fragile a project is.
version	3.0.0
kind	pipeline
triggers	["analyze this repo","repo reliability report","how reliable/fragile is this project","analyze commit patterns","run repo reliability on <repo>"]
intent	analysis
config_dir	~/.config/skill-config/repo-reliability
created_at	2026-07-28T00:00:00.000Z
updated_at	2026-07-30T00:00:00.000Z
guardrails	["Read-only against the analyzed repository — never modify, commit, or push to it","Forge (GitHub) pointers need an authenticated gh CLI; when unavailable, skip them gracefully and still deliver the git-only report — never block on forge access","Metrics measure process health, a proxy for reliability — present bands with their evidence, never as verdicts on code quality"]
resources	["<SKILL_PATH>/scripts/run-report.sh","<SKILL_PATH>/scripts/rr_build.py","<SKILL_PATH>/scripts/rr_common.py","<SKILL_PATH>/webapp/app.json","<SKILL_PATH>/references/envelope.md"]
tools	["bash","git","gh","jq","python3"]

Repo reliability

Runs every pointer under pointers/ against a repo. Each pointer is a self-contained folder (pointer.json definition + run.sh script) that emits one JSON envelope (schema: references/envelope.md). The runner stores one bundle per project in mosaic's centralized data home and refreshes a manifest; webapp/ is a mosaic dashboard tile (data-app-backed skill, see skill-creator/references/data-app-skills.md) rendering all analyzed projects: a project list, per-project card dashboard, and click-through detail visuals per card.

Configuration

~/.config/skill-config/repo-reliability/skill.properties — created with defaults on first run; report loaded values to the user:

• data_home (default ~/.local/share/repo-reliability) — clones of URL-analyzed repos, in clones/. Project bundles and the manifest the webapp reads live in mosaic's own data home instead (~/.local/share/mosaic/data/repo-reliability/), not here.
• window_months (default 12) — analysis window for time-boxed pointers
• forge_pr_limit / forge_issue_limit (default 300) — API fetch caps
• mosaic_onboarded — internal flag set once the webapp has been symlinked into mosaic's staging dirs; not user-tunable

Do not add new properties without explicit user approval.

Workflow

1. Identify the target: a local path or a repo URL (URL → the runner clones into <data_home>/clones/). Rerunning on the same remote replaces that project's stored JSON — project identity is keyed on the remote URL.

2. Run: <SKILL_PATH>/scripts/run-report.sh --repo <path-or-url> Useful flags: --months N, --no-forge, --render-only (rebuild manifest.json from stored data without analyzing), --open.

3. The runner onboards itself into mosaic on first run (idempotent after) and prints the project's data file plus the dashboard URL (http://localhost:<mosaic-port>/mosaic/apps/repo-reliability/, default port 47500). Relay both to the user.

4. Deliver: tell the user to start mosaic if it isn't already running ($TOOLS_PATH/mosaic/quick-start.sh start) then open the dashboard URL. does this automatically via . There is no standalone report file to hand over — mosaic is the only rendering surface.