learn

Analyze repository structure and generate eight knowledge files with citations.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/minhquan2904/vibe-check-scam --skill learn-minhquan2904
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: learn
Source: https://github.com/minhquan2904/vibe-check-scam/tree/main/.agent/skills/learn
Command: npx skills add https://github.com/minhquan2904/vibe-check-scam --skill learn-minhquan2904

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams quickly understand a codebase and generate structured knowledge artifacts that power the propose and apply phases of the pipeline.

Core Features & Use Cases

  • Systematically analyzes repository structure, modules, services, and data access patterns to produce actionable knowledge.
  • Generates eight knowledge files plus a features registry to guide future development and maintenance.
  • Organizes outputs in base_knowledge/structures/propose/ and base_knowledge/structures/apply/ with clear module-level citations.

Quick Start

Run the learn skill to analyze the repository and generate the eight knowledge files and features registry.

Frequently Asked Questions about learn

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

FAQPage Schema
How do I analyze a codebase structure and generate knowledge artifacts?

Codebase analysis for knowledge generation covers repository structure, solution layout, domain modules, services, and data access patterns, producing eight knowledge files and a features registry with citations to actual class names and file paths.

How do I automatically document repository architecture and data access patterns?

You generate structured knowledge by running an analysis that outputs eight knowledge files plus a features registry, organizing them in base_knowledge/structures/propose/ and base_knowledge/structures/apply/ directories to guide future development.

What is the best way to extract domain modules and services from an existing codebase?

Yes, you can use codebase analysis to generate knowledge artifacts for the propose and apply phases, outputting structured files that map repository structure, domain modules, services, and data access patterns to guide future maintenance.

Does the generated codebase knowledge include actual class names and file paths?

Codebase analysis outputs eight knowledge files plus a features registry, storing them under base_knowledge/structures/propose/ and base_knowledge/structures/apply/ directories to systematically map repository structure, domain modules, services, and data access patterns.

Can I generate structured knowledge files for propose and apply development phases?

Codebase analysis identifies repository structure, solution layout, domain modules, services, and data access patterns, generating eight knowledge files and a features registry with citations to actual class names and file paths without using placeholders.

Are there limitations when analyzing codebase architecture to generate knowledge files?

Codebase analysis generates eight knowledge files and a features registry under base_knowledge/structures/propose/ and apply/ directories, mapping repository structure, domain modules, services, and data access patterns with citations to actual class names and file paths.