init

Scan codebases to inventory public-facing pages into .overgrow/inventory.md.

7|Updated Mar 29, 2026
One-click install
npx skills add https://github.com/zhizdev/overgrow --skill init-zhizdev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: init
Source: https://github.com/zhizdev/overgrow/tree/main/.cursor/skills/init
Command: npx skills add https://github.com/zhizdev/overgrow --skill init-zhizdev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates discovery and documentation of all public-facing pages to provide a baseline site map and inventory.

Core Features & Use Cases

  • Scans the codebase to detect homepage, product pages, blogs, docs, legal pages, and other public routes.
  • Outputs a structured .overgrow/inventory.md containing product summary, routing, authoring conventions, and per-page inventory to serve as a single source of truth for other Overgrow skills.
  • Supports framework detection and multiple routing conventions to adapt to Next.js, Astro, Nuxt, and other stacks.
  • Use case: Quickly establish a baseline inventory to guide page creation, migration, and SEO planning.

Quick Start

Run the project root scan or specify a site path with $ARGUMENTS to generate the inventory document.

Frequently Asked Questions about init

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

FAQPage Schema
How do I build a site inventory from my codebase?

To build a site inventory from your codebase, run a project root scan to detect public-facing pages, apply framework hints, extract frontmatter, and output a structured .overgrow/inventory.md file.

Does site inventory routing detection work with Next.js and Astro?

Site inventory routing detection supports multiple routing conventions and adapts to frameworks including Next.js, Astro, and Nuxt to accurately discover and categorize public routes across different stacks.

How are pages categorized when scanning public-facing routes?

Pages are categorized by applying route discovery and front-matter extraction to classify public-facing routes into homepage, product, blog, docs, legal, and other categories within the generated inventory.

What is the best way to automate site map generation for SEO planning?

The best way to automate site map generation for SEO planning is scanning the codebase to establish a baseline inventory, providing a single authoritative source of truth for routing and authoring conventions.

Why generate an inventory.md file for site-scans?

You generate an inventory.md file because it serves as a single source of truth containing the product summary, routing, and per-page inventory, ensuring baseline data consistency for future site-scans.