repo-scout

Audit Go backend repositories for API endpoints, infrastructure, and test coverage.

25|14|Updated Feb 1, 2026
One-click install
npx skills add https://github.com/vlad-ryzhkov/AI-QA-workshop-feb19 --skill repo-scout-vlad-ryzhkov
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repo-scout
Source: https://github.com/vlad-ryzhkov/AI-QA-workshop-feb19/tree/main/.agents/skills/repo-scout
Command: npx skills add https://github.com/vlad-ryzhkov/AI-QA-workshop-feb19 --skill repo-scout-vlad-ryzhkov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scan and catalog the surface area of a Go backend repository, including API endpoints, infrastructure layout, and test coverage, to establish a baseline for quality gates and audits.

Core Features & Use Cases

  • Identify API surface by packages and endpoints, including handler routes and public interfaces.
  • Inventory infrastructure components such as modules, services, and deployment concerns to support architectural reviews.
  • Assess test coverage and structure to guide QA planning and test generation.

Quick Start

Scan a new Go repository to generate an initial repo-scout audit detailing API surface, infrastructure, and test coverage.

Frequently Asked Questions about repo-scout

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

FAQPage Schema
How do I audit a Go backend repository's API surface and test coverage?

To audit a Go backend repository, you can scan it to catalog API endpoints, inventory infrastructure components, and assess test coverage. This establishes a baseline for quality gates.

What is a Go API surface audit and when do I need one?

A Go API surface audit identifies handler routes and public interfaces across packages. You need one when onboarding new Go projects to establish a baseline of endpoints and testing guarantees.

How do I map infrastructure footprint and modules in a Go project?

To map infrastructure footprint in a Go project, inventory modules, services, and deployment concerns. This details the infrastructure layout to support architectural reviews.

Can I assess Go test coverage and structure across all packages?

Yes, you can assess Go test coverage and structure across all packages. The audit evaluates test suites to guide QA planning and test generation.

Do I need knowledge of Go project structure to map endpoints and modules?

Yes, mapping endpoints and modules requires knowledge of Go project structure and module graphs. This understanding is necessary to deliver a structured audit of surface area.