local-repo-check

Scan local Git repositories for code, tests, and commit history to determine component implementation status.

2|Updated Jan 11, 2026
One-click install
npx skills add https://github.com/my-entourage/entourage-plugin --skill local-repo-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: local-repo-check
Source: https://github.com/my-entourage/entourage-plugin/tree/main/skills/local-repo-check
Command: npx skills add https://github.com/my-entourage/entourage-plugin --skill local-repo-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scans local Git repositories to verify whether a component is actually implemented by locating matching source files, tests, and relevant commit history.

Core Features & Use Cases

  • Evidence-based verification: finds code and tests for a given component across configured repos and reports status.
  • Status synthesis: returns Complete, In Progress, or Unknown based on the presence of code, tests, and main-branch history.
  • Optional discovery: auto-discovers local repo paths when explicit mappings are missing, enabling seamless ongoing checks.

Quick Start

Invoke the skill with a component name to scan local repositories for code, tests, and history evidence.

Frequently Asked Questions about local-repo-check

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

FAQPage Schema
How do I verify if a feature is actually implemented in local Git repositories?

Scanning local Git repositories for code, tests, and commit history verifies feature implementation. This process synthesizes evidence to report status as Complete, In Progress, or Unknown based on the discovered artifacts.

How do I check the status of a component across multiple local repos?

Checking component status across multiple local repos involves locating matching source files and tests. The scanner returns Complete, In Progress, or Unknown statuses by validating evidence across all configured repositories simultaneously.

How does automatic path discovery work for missing local repository mappings?

Automatic path discovery enables seamless ongoing checks by auto-discovering local Git repository paths when explicit mappings are missing. This allows the scanner to locate and verify code without requiring manual configuration for every repository.

Do I need to configure repositories before checking for code evidence?

You can configure repositories via .entourage/repos.json and optional path mappings via .entourage/paths.local.json, but explicit configuration is not required. The scanner automatically discovers local repository paths when mappings are missing to find code evidence.

What is the best way to use Git history for feature validation and compliance checks?

Using Git history for feature validation involves scanning local repositories for relevant commits alongside source code and tests. This evidence-based method supports compliance checks by reporting whether a component is Complete, In Progress, or Unknown.

Why does my local repository scan return an Unknown status for a component?

A local repository scan returns an Unknown status for a component when insufficient evidence is found. This occurs when matching source files, tests, or main-branch commit history cannot be located within the configured or discovered repositories.