repo-intake

Generate a markdown/json repository cache with entrypoints and tests.

187|24|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/sd0xdev/sd0x-dev-flow --skill repo-intake
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repo-intake
Source: https://github.com/sd0xdev/sd0x-dev-flow/tree/main/skills/repo-intake
Command: npx skills add https://github.com/sd0xdev/sd0x-dev-flow --skill repo-intake

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the initial repository onboarding by inventorying the project and generating a reusable cache, reducing manual setup time for new workstreams.

Core Features & Use Cases

  • One-time inventory: Scans the repository to identify entrypoints, tests, and a recommended next steps list.
  • Cache generation: Produces a markdown/json cache that can be reused across sessions.
  • Use Case: Ideal for onboarding a new project or after major structural changes to establish a project map and baseline.

Quick Start

Run the intake script to generate the initial cache, for example: node skills/repo-intake/scripts/intake_cached.js --mode auto --top 10

Frequently Asked Questions about repo-intake

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

FAQPage Schema
How do I automate repository onboarding and generate a project map?

To automate repository onboarding, run the intake script to scan via git and filesystem, producing a markdown/json project map cache that identifies entrypoints, tests, and recommended next steps.

What is a repository intake cache and when do I need to generate one?

A repository intake cache is a stable markdown/json map of project entrypoints and tests. You generate one when first onboarding a new project or after major structural changes to establish a baseline.

How do I scan a git repository structure to find entrypoints and tests?

You scan a git repository structure to find entrypoints and tests by running an intake script that analyzes the filesystem and produces a markdown/json cache inventory for the project.

Can I reuse the project inventory cache across multiple sessions?

Yes, you can reuse the project inventory cache across sessions because the intake process produces stable markdown and json files designed to support downstream tooling and reduce manual setup time.

When should I regenerate the repository inventory cache?

You should regenerate the repository inventory cache after major structural changes to the project, ensuring the markdown/json map accurately reflects current entrypoints, tests, and recommended next steps.