project-mapper

Generate codebase_map.json classifying files as value or noise from scan_results.json.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Swear4/agent_rules --skill project-mapper-swear4
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-mapper
Source: https://github.com/Swear4/agent_rules/tree/main/agent-universal/skills/project-mapper
Command: npx skills add https://github.com/Swear4/agent_rules --skill project-mapper-swear4

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Cartographier le codebase pour identifier TOUS les fichiers contenant de la logique métier et générer un codebase_map.json exhaustif, pour une vue unique et fiable du produit.

Core Features & Use Cases

  • Cartographier l'ensemble des fichiers sources sans interprétation pour produire une map exhaustive.
  • Détecter les changements structurels et déclencher le pipeline de cartographie avant l'extraction de fonctionnalités.
  • Use Case: Lors de l'initialisation d'un projet, générer le codebase_map.json et servir de mémoire structurelle pour les phases suivantes.

Quick Start

Lancez le scan et générez un codebase_map.json exhaustif à partir des résultats.

Frequently Asked Questions about project-mapper

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

FAQPage Schema
How do I generate an exhaustive codebase map of all business logic files?

Mapping your codebase at project initialization identifies all business logic files before feature extraction. It relies on exact line counts from scan_results.json to inventory sources, detect structural changes, and serve as a structural memory for the pipeline.

How does codebase mapping classify source files as value or noise?

Codebase mapping classifies source files by relying on exact line counts extracted from scan_results.json. It evaluates each file to determine if it contains business logic, categorizing it as value or noise to ensure no file is invented during the inventory process.

Do I need scan_results.json to map my codebase for feature extraction?

You need scan_results.json because the mapping process relies on exact line counts from this file to accurately inventory all sources, detect structural changes, and populate valueClusters for downstream miners.

What is the best way to inventory source files without inventing missing files?

The best way to inventory source files is to use an exhaustive codebase mapping process that strictly relies on exact line counts from scan_results.json. This ensures no file is invented and all business logic files are accurately classified.

Can codebase mapping detect structural changes in a software pipeline?

Yes, codebase mapping can detect structural changes in a software pipeline. By producing an exhaustive codebase_map.json at project initialization, it tracks the inventory of business logic files and triggers updates before feature extraction.