gvm-site-survey

Diagnose codebase health and recommend GVM pipeline entry points.

5|Updated May 4, 2026
One-click install
npx skills add https://github.com/gerquinn1978/gvm --skill gvm-site-survey
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gvm-site-survey
Source: https://github.com/gerquinn1978/gvm/tree/main/grounded-vibe-methodology/skills/gvm-site-survey
Command: npx skills add https://github.com/gerquinn1978/gvm --skill gvm-site-survey

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

The gvm-site-survey skill provides a comprehensive diagnostic and health assessment of existing codebases, helping users understand their current state and guiding them towards the most suitable entry point in the GVM pipeline.

Core Features & Use Cases

  • Codebase Diagnostics: Scores the codebase across multiple dimensions for coherence, currency, testability, modularity, documentation, and dependency health.
  • Architectural Mapping: Identifies patterns, boundaries, data flow, and conventions in the codebase.
  • Expert Selection: Assembles a tailored expert panel based on the diagnosis and tech stack for downstream pipeline phases.
  • Route Recommendation: Recommends the appropriate GVM pipeline entry point (e.g., requirements, technical specification, build) based on the diagnosis and nature of the intended work.
  • Use Case: When starting work on an existing codebase, use gvm-site-survey to understand the system's architecture, identify areas of concern, and recommend the next steps in the GVM process.

Quick Start

Run the gvm-site-survey skill to assess your codebase's health and architecture.

Frequently Asked Questions about gvm-site-survey

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

FAQPage Schema
How do I assess codebase architecture before starting modernization work?

To assess codebase architecture for modernization, you conduct a diagnostic survey that scores coherence, modularity, and dependency health. This analysis identifies architectural patterns, boundaries, and data flow to determine the system's current state and guide remediation efforts.

What is a codebase diagnostic survey and when do I need it?

A codebase diagnostic survey is a comprehensive health assessment of source code, configuration files, and version control history. You need it when starting work on an existing codebase to understand the system's architecture, identify areas of concern, and recommend next steps.

How do I select the right entry point for a pipeline based on my codebase health?

To select the right pipeline entry point, you run a diagnostic assessment that scores codebase health across multiple dimensions. Based on the diagnosis and nature of intended work, it recommends the appropriate starting phase, such as requirements, technical specification, or build.

Can I map architectural boundaries and data flow in an existing codebase automatically?

You can map architectural boundaries and data flow by running an automated diagnostic assessment. It analyzes source code and configuration files to identify patterns, conventions, and structural boundaries within the existing system architecture.

Does the codebase assessment work with any tech stack or does it require specific configuration?

The codebase assessment operates on source code, configuration files, and version control history to evaluate tech stack health. It selects tailored expert systems based on the diagnosis to guide remediation and modernization efforts across different stacks.

What are the limitations of automated codebase health assessments for modernization?

Automated codebase health assessments are limited to analyzing source code, configuration files, and version control history. They provide diagnostic scores and recommendations but do not execute remediation directly; they guide downstream pipeline phases instead.