Indexer un dossier

VérifiéSûr

Indexe les fichiers pris en charge (Markdown, JSON) d'un dossier dans un fichier d'index de contexte pour une récupération rapide. Extrait des métadonnées comme le titre, le type, les sujets et la phase V2V. Aide à cataloguer et découvrir rapidement les documents du projet.

Spar Skills Guide Bot
DocumentationIntermédiaire
7002/06/2026
Claude Code
#folder-indexing#context-management#document-catalog#file-discovery#retrieval

Recommandé pour

Notre avis

Cette compétence scanne un dossier et indexe son contenu dans un système de contexte pour une récupération rapide par sujet.

Points forts

  • Indexation automatisée des fichiers pris en charge (.md, .json) avec extraction de métadonnées.
  • Détection intelligente des types de documents (PRD, décision, roadmap, etc.) et des phases V2V.
  • Mise à jour incrémentielle de l'index sans dupliquer les entrées inchangées.
  • Génération d'un rapport structuré avec résumé des sujets.

Limites

  • Limité aux fichiers .md et .json, ignore les autres formats.
  • Nécessite une structure de projet compatible et le fichier context/index.json préexistant.
  • Ne fonctionne pas avec des fichiers de plus de 100 Ko ou dans les répertoires exclus (node_modules, .git, etc.).
Quand l'utiliser

Utilisez cette compétence lorsque vous devez cataloguer rapidement l'ensemble des documents d'un dossier pour faciliter leur découverte et leur référencement dans le contexte.

Quand l'éviter

Ne l'utilisez pas pour sauvegarder des décisions dans le contexte (utilisez /context-save) ou pour des opérations de recherche ponctuelles sans besoin d'indexation persistante.

Analyse de sécurité

Sûr
Score qualité90/100

The skill only reads files and writes to a local index.json within the project. It uses Read, Write, Edit, and Glob tools but does not execute any external commands or scripts. It skips sensitive directories and large files. No risk of data exfiltration or system compromise.

Aucun point d'attention détecté

Exemples

Index a folder
/index-folder documents/prd
Recursive folder indexing
/index-folder documents --recursive
Index by document type
/index-folder documents --type decision

name: index-folder description: | Index a folder's contents into the context system for fast retrieval and discovery. Activate when: "index this folder", "catalog these files", folder contents indexed, build file index, scan folder Do NOT activate for: saving decisions to context (/context-save), recalling context (/context-recall), plugin setup (/setup) model: haiku allowed-tools:

  • Read
  • Write
  • Edit
  • Glob user-invocable: true metadata: author: Product Org OS version: 3.0.0 category: context-layer compatibility: Requires Product Org OS v3+ context layer and rules

Index Folder

Scan a folder and add its contents to context/index.json for fast topic-based retrieval.

Trigger Patterns

  • /index-folder [path] - Index all supported files in path
  • /index-folder [path] --recursive - Include subfolders
  • /index-folder [path] --type [type] - Only index specific type

Behavior

1. Validate Path

Confirm the path exists and is accessible:

  • Accept relative paths from project root
  • Accept absolute paths
  • Reject paths outside the project

2. Scan for Supported Files

Supported file types:

  • .md - Markdown documents
  • .json - JSON data files (skip package.json, node_modules)

Always skip:

  • node_modules/
  • .git/
  • __pycache__/
  • .venv/, venv/
  • dist/, build/
  • Files starting with .
  • Files over 100KB (likely not documents)

3. Extract Metadata

For each file, extract:

{
  "id": "DOC-YYYY-NNN",
  "title": "[H1 or filename]",
  "type": "[detected type]",
  "path": "[relative path]",
  "topics": ["topic1", "topic2"],
  "phase": "[V2V phase if detectable]",
  "created": "[file creation date]",
  "lastAccessed": "[current date]",
  "size": "[file size]"
}

Type Detection: | Pattern | Type | |---------|------| | Contains "PRD" or in prd/ | prd | | Contains "Decision Record" or DR- | decision | | Contains "Strategic Bet" or SB- | bet | | Contains "Roadmap" | roadmap | | Contains "GTM" or "Go-to-Market" | gtm | | Contains "Analysis" | analysis | | Contains "Feedback" or FB- | feedback | | Contains "Learning" or L- | learning |

Topic Extraction:

  • Extract from document headers (H1, H2)
  • Extract from tags if present in frontmatter
  • Extract key nouns from first paragraph
  • Limit to 5-10 topics per document

Phase Detection: Look for V2V phase indicators:

  • "Strategic Foundation" → phase1
  • "Strategic Decision" → phase2
  • "Commitment" or "Roadmap" → phase3
  • "Execution" or "Launch" → phase4
  • "Outcome" or "Value" → phase5
  • "Learning" or "Retrospective" → phase6

4. Update Index

Read context/index.json and:

  1. Add new entries - Files not already indexed
  2. Update existing entries - Files that have changed (by path)
  3. Update topicIndex - Add document IDs to topic arrays
  4. Update typeIndex - Add document IDs to type arrays
  5. Update phaseIndex - Add document IDs to phase arrays
  6. Update lastUpdated - Set to current date

5. Output Report

# Folder Indexed: [path]

**Scanned**: [N] files
**Added**: [N] new entries
**Updated**: [N] existing entries
**Skipped**: [N] (already indexed, unchanged)

## New Entries

| ID | Title | Type | Topics |
|----|-------|------|--------|
| DOC-2026-015 | Authentication PRD | prd | auth, security, login |
| DOC-2026-016 | Pricing Decision | decision | pricing, enterprise |

## Topic Summary

| Topic | Documents |
|-------|-----------|
| authentication | 5 |
| pricing | 3 |
| enterprise | 3 |
| security | 2 |

---

*Index updated at context/index.json*

Index Format

The context/index.json structure:

{
  "version": "1.0",
  "lastUpdated": "2026-01-25",
  "entries": [
    {
      "id": "DOC-2026-001",
      "title": "Authentication PRD",
      "type": "prd",
      "path": "documents/prd-auth.md",
      "topics": ["authentication", "security", "login", "oauth"],
      "phase": "phase3",
      "created": "2026-01-15",
      "lastAccessed": "2026-01-25",
      "size": 4520
    }
  ],
  "topicIndex": {
    "authentication": ["DOC-2026-001", "DOC-2026-005"],
    "pricing": ["DOC-2026-003", "DOC-2026-007"]
  },
  "typeIndex": {
    "prd": ["DOC-2026-001"],
    "decision": ["DOC-2026-003"],
    "bet": ["DOC-2026-002"]
  },
  "phaseIndex": {
    "phase1": ["DOC-2026-010"],
    "phase2": ["DOC-2026-003"],
    "phase3": ["DOC-2026-001", "DOC-2026-005"]
  }
}

ID Generation

Generate unique IDs:

  • Format: DOC-YYYY-NNN
  • YYYY = current year
  • NNN = sequential number (001, 002, ...)
  • Check existing entries to avoid collisions

Notes

  • Indexing is additive - existing entries are preserved
  • To remove stale entries, use /index-cleanup
  • Large folders may take time - provide progress updates
  • Topics are normalized to lowercase
  • Duplicate entries (same path) are updated, not duplicated
Skills similaires