repo-summary-and-relation-mapping

Analyzes local git repositories and writes short summaries mapping relationships between sibling repos.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/amitkarpe/agent-skills --skill repo-summary-and-relation-mapping-amitkarpe
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: repo-summary-and-relation-mapping
Source: https://github.com/amitkarpe/agent-skills/tree/main/skills/repo-summary-and-relation-mapping
Command: npx skills add https://github.com/amitkarpe/agent-skills --skill repo-summary-and-relation-mapping-amitkarpe

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? When managing many local repositories, it becomes hard to remember what each repo owns, where boundaries overlap, and what should be consolidated or migrated. This Skill produces short, objective repo summaries and relation maps so cleanup and decomposition decisions are grounded in facts rather than guesswork. ## Core Features & Use Cases - Automated Fact Collection: The collect-repo-facts.sh script gathers git branch, remote URL, top-level files, and previews of README.md, ROADMAP.md, PLANS.md, and AGENTS.md. - Sibling Repo Comparison: Accepts multiple related repo paths to compare boundaries, overlaps, and migration direction across a repo set. - Reusable Local Summaries: Writes a short repo-summary.md under ~/.AGENTS-temp/<repo-name>/ for later migration or consolidation work. - Use Case: Before decomposing a monorepo or cleaning up repo sprawl across repos like infra, packer, and awsops, run the fact collector on each repo and produce a summary covering each repo's object, owned artifacts, and relation to siblings. ## Quick Start Run the repo summary skill on my local repository and its sibling repos to write a short objective summary and relation map under ~/.AGENTS-temp.

Frequently Asked Questions about repo-summary-and-relation-mapping

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I summarize what a local git repository does?▼

Run the collect-repo-facts.sh script with the repo path to gather its git branch, remote URL, top-level files, and previews of README.md, ROADMAP.md, PLANS.md, and AGENTS.md. Use that output to write a short summary covering the repo's object, owned artifacts, and boundaries.

How to compare multiple repos before consolidation or cleanup?▼

Pass the target repo plus related repo paths to collect-repo-facts.sh, which prints branch, remote, and top-level listings for each. Then write a relation section covering overlaps, boundaries, and migration direction between the sibling repos.

Where should repo summary output files be written?▼

Write summaries under ~/.AGENTS-temp/<repo-name>/, typically as repo-summary.md. Do not write them to /tmp, so the summaries remain reusable for later migration or consolidation work.

When should I not use repo summary and relation mapping?▼

Skip it when you only need a code walkthrough of a single module or when the task is editing application code rather than classifying repo boundaries. It is designed for repo-level organization decisions, not code-level changes.

Does the repo facts script require git to be installed?▼

Git is used to read branch and remote information, but the script handles non-git directories gracefully by skipping the git section. It still lists top-level files and previews documentation files when present.