repo-activity-summary SKILL.md skillA
repo-activity-summary from codealive-ai/ai-driven-development is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add codealive-ai/ai-driven-development/repo-activity-summary@v1.1.0Pins v1.1.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- codealive-ai/ai-driven-development
- Path
skills/repo-activity-summary/SKILL.md- Versions recorded
- 2
- Latest version
- v1.1.0, committed Aug 6, 2026
- First version recorded
- Aug 6, 2026
- Size
- 4,868 bytes
- Repository stars
- 167
- License
- MIT
Summarize a repository's recent engineering activity from git history — technologies, work types, churn hotspots, contributor patterns, and velocity. Use when asking "what has this repo been working on", "is this project active", "who contributes what", "where are the hotspots", or before onboarding onto an unfamiliar codebase.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Repo Activity Summary Answer "what's been happening in this repo" from local git history — no network, no tokens, no setup. ## Trigger conditions Use this skill when the user asks: - "What has this repo been working on recently?" - "What technologies does this project use?" - "Where are the high-churn files / hotspots?" - "Who's contributing and what are they working on?" - "Is this project actively maintained?" - Before onboarding onto an unfamiliar codebase. Do not use this skill for file-level blame or provenance — use `investigating-repository-history` for that. ## Quick start ```bash python3 scripts/activity_summary.py --repo-dir . --days 90 ``` | Flag | Default | Description | |------|---------|-------------| | `--repo-dir` | `.` | Path to the git repository | | `--days` | `90` | Days of history to analyze | | `--author` | *(all)* | Filter to one author | | `--format` | `markdown` | `markdown`, `json`, or `text` | | `--max-commits` | `500` | Cap for very active repos | | `--branch` | *(current)* | Branch / revision to analyze (must not start with `-`) | | `--output` / `-o` | *(stdout)* | Write the report to a file (UTF-8) | …
Read the whole file at its exact version.
How to install
mdr add codealive-ai/ai-driven-development/repo-activity-summary@sha256:2b4290960ecb6696The line at the top of this page pins the label v1.1.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_vpma7gpjayom734k)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, all committed on Aug 6, 2026.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.1.0 latest | 2026-08-06 | 1d4bd7e | 4,868 B | A | view · diff |
| v1.0.0 | 2026-08-06 | 5ec51b0 | 2,905 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (4868 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
codealive-ai/ai-driven-development · 167 stars · license MIT · pushed 2026-11-05 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_vpma7gpjayom734k GET https://markdownregistry.com/api/v1/resolve?ref=codealive-ai/ai-driven-development/repo-activity-summary GET https://markdownregistry.com/api/v1/blob/2b4290960ecb669620bda167576b9a7c042d71ad17edcdddeafe689591df7f60
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.