skills.rest
atman-33
atman-33COMMUNITY
Explore all skills by this author →
Website𝕏@atman_33GitHub

multi-repo-review

Extract diffs across VSCode workspace repositories and generate a consolidated markdown review report.

Updated Feb 7, 2026
Search Tags:#multi-repo#code-review#cross-repo#ai-review#report-generation#git-diffs
One-click install
npx skills add https://github.com/atman-33/atman-workspace --skill multi-repo-review
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: multi-repo-review
Source: https://github.com/atman-33/atman-workspace/tree/main/skills/multi-repo-review
Command: npx skills add https://github.com/atman-33/atman-workspace --skill multi-repo-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, git, and includes scripts (resource) components.

What problem does it solve?

Cross-repo code review across multiple repositories helps teams detect inconsistencies in API contracts, type definitions, dependencies, and integration points that single-repo reviews might miss. It enables extracting diffs from all repos within a VSCode workspace and applying AI-powered analysis using configurable guidelines.

Core Features & Use Cases

  • Cross-repo diff extraction across a VSCode workspace containing multiple repositories to surface cross-project discrepancies.
  • Unified AI-powered review against a set of configurable guidelines to highlight API contract alignment, type definition drift, dependency conflicts, and authentication flow issues.
  • Consolidated markdown report generation suitable for PRs and documentation to communicate findings across teams.

Quick Start

Configure a VSCode workspace with multiple repositories and run the extraction script to generate a cross-repo review report.

Frequently Asked Questions about multi-repo-review

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

FAQPage Schema
How do I perform a cross-repo code review to catch API contract mismatches and type definition drift?▼

Cross-repo code review is automated by extracting git diffs from multiple repositories within a VSCode workspace and analyzing them against configurable guidelines to detect API contract mismatches, type drift, and dependency conflicts across projects.

What is the best way to review integration gaps across multiple repositories in a single workspace?▼

Reviewing integration gaps across multiple repositories is handled by applying AI-powered analysis to unified git diffs against a review-guidelines file, generating a consolidated markdown report highlighting cross-project inconsistencies and auth flow issues.

Do I need git and jq installed to run a cross-repo AI review?▼

Yes, git and jq are required dependencies. The workflow uses git to extract per-repo base branch diffs and jq to process data for the AI-powered analysis, ultimately producing a consolidated markdown report.

Can I use this workflow to review frontend, backend, and shared libraries simultaneously?▼

Yes, you can review frontend, backend, and shared libraries simultaneously by configuring a VSCode workspace with multiple repositories. The workflow extracts diffs from all included repos and applies unified AI-powered analysis to surface discrepancies.

How do I configure per-repo base branches for a multi-repo code review?▼

Configuring per-repo base branches requires setting up a VSCode workspace with your target repositories and defining a review-guidelines file. The extraction script then uses these configurations to extract diffs and run cross-repo analysis.

What are the limitations of automated cross-repo code analysis?▼

Automated cross-repo code analysis is limited to detecting issues defined in your review-guidelines file and requires a VSCode workspace setup. It cannot detect issues outside the extracted git diffs or analyze uncommitted local changes.

Related Skills

Explore More Software Engineering Skills→
gullitmirandagullitmiranda
2

workspace-status

Generate a per-repo status overview for multi-repo git workspaces.

Community
Intermediate
NoSugarCoffeeNoSugarCoffee
1

code-review

Identify and communicate high-signal issues in code changes with actionable feedback.

Community
Advanced
encero-systemsencero-systems
92

create-pr-description

Generate PR descriptions from repository templates and git diff changes.

Official
Intermediate
benjaminshoemakerbenjaminshoemaker
39

update-docs

Analyze commit ranges or working tree changes to update documentation files.

Community
Advanced