collect-github-stats

Solid

Collect GitHub repo health/usage stats into merged JSON.

AI & Automation 344 stars 75 forks Updated 1 weeks ago Apache-2.0

Install

Quality Score: 83/100

Stars 20%

85

Recency 20%

90

Frontmatter 20%

70

Documentation 15%

61

Issue Health 10%

50

License 10%

100

Description 5%

100

Skill Content

# collect-github-stats Runs one script: fetch GitHub stats for a repo, merge into `docs/github-stats.json`. ## Run (MUST) ```bash python3 <skill_dir>/scripts/collect_stats.py [--repo OWNER/NAME] [--out PATH] [--no-enrich] ``` Defaults: `--repo griddynamics/rosetta`, `--out docs/github-stats.json`. MUST run from repo root (or pass absolute `--out`). `--no-enrich` skips company/location lookups. ## CRITICAL - **NEVER DELETE OR OVERWRITE `docs/github-stats.json`.** Script APPEND-MERGES. Traffic is a 14-DAY ROLLING WINDOW — deleted history is GONE FOREVER, unrecoverable from the API. - **PUSH ACCESS REQUIRED.** No push → traffic 403 → script FAILS LOUD with fix steps. MUST NOT accept a partial file. ## Rules (MoSCoW) - MUST have `gh` authenticated, `repo` scope, push access to the target repo. - SHOULD relay the script's post-run summary to the user. - COULD normalize company variants when REPORTING; MUST NOT mutate stored raw values. - WON'T fabricate cloner identity (cloners are ANONYMOUS — counts only), store PII/secrets. ## Lessons learned (keep updating, first line is template, follow <instructions>) - **<key action item>** <concise: what happened, why, root cause, reasoning>.

Details

Author: griddynamics
Repository: griddynamics/rosetta
Created: 7 months ago
Last Updated: 1 weeks ago
Language: TypeScript
License: Apache-2.0

Integrates with

GitHub · DevTools

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Listed

gh-metrics

Use when asked how often a GitHub repo merges pull requests, average or median time to merge, PR throughput, review turnaround, open-PR backlog, or how often RFC/proposal issues get accepted and how long they take. Computes repository PR and issue/RFC metrics consistently via the gh CLI.

0 Updated 1 months ago

Code & Development Listed

github-status

List your GitHub-owned local clones under PROJECTS_ROOT that have pending work (uncommitted changes, unpushed commits, or inbound remote commits), with branch, counts, age of oldest pending work, open-issue count, and a per-repo summary. Each run fetches every repo's origin in parallel so the counts reflect the current remote. TRIGGER when: user asks "/github-status", wants a cross-project overview of their repos, "which repos have unpushed commits", "what's new on remotes", or "what have I been working on". DO NOT TRIGGER when: user is asking about a single specific repo (use `git status` / `git log` directly).

1 Updated 2 days ago

Code & Development Listed

github-repo-hygiene

Audits a GitHub profile or specific repos for the things that make a developer look inactive or unpolished to anyone vetting them — missing repo descriptions, missing topics, no license, and READMEs that are still unedited framework boilerplate (create-next-app, create-react-app, etc). Reports what it finds, then fixes whatever the user approves by writing real descriptions and topics and rewriting thin READMEs into an actual project overview. Use this whenever the user wants to clean up their GitHub, make their profile look more professional for recruiters/clients, audit their repos, mentions their GitHub looking sparse/empty/unfinished, or is prepping their profile for a job search or freelance pitch — even if they don't say "hygiene" or name a specific repo.

0 Updated 5 days ago