feat: index Markdown files

Abierto
#115 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
18/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
go, markdown
Área
tooling

Línea de trabajo

Start with internal/indexer/discover_test.go at lines 206 and 235, which assert that README.md is never discovered, and with the language entries in internal/indexer/languages_<lang>.go. The first decision is what a Markdown symbol is (headings, links, code fences) and whether it fits the graph vocabulary; this needs maintainer input before any code. Done means a recorded vocabulary decision, a discover test changed with a stated reason, and an updated capability matrix.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

area:indexer feature priority:low spec-needed
What problem does this solve?

Documentation in Markdown (READMEs, ADRs, runbooks) is invisible to explore, search and the MCP tools, so an agent cannot reach docs through the graph.

What should it do?

To be decided first: what a Markdown "symbol" is (headings, links, code fences) and whether it belongs in the same graph vocabulary as functions and types. Then add a language entry following internal/indexer/languages_<lang>.go.

Which surface does this affect?

Indexing / extraction

Is this covered by an existing command or tool today?

No. .md is excluded by assertion, not by omission: internal/indexer/discover_test.go:206,235 asserts README.md is never discovered, so this change must narrow or replace that test deliberately. No tree-sitter-markdown grammar is vendored (go.mod). The upstream grammar is split into block and inline parsers, which does not fit the one-grammar-per-language registry. A new CGo dependency also enters the SBOM and the govulncheck set.

Acceptance criteria
  • A recorded vocabulary decision.
  • The discover test changed with a stated reason.
  • The capability matrix updated.

Source (GSD planning files, archived at d384473e): .planning/seeds/SEED-003-markdown-in-the-index.md


🤖 Generated with Claude Code

https://claude.ai/code/session_01UNqdnC3q6U362BvyfxuKCF

Lenguaje dominante
Go
Estrellas
0
Forks
0
Merge medio
7 h 42 min
PR fusionados (30 d)
111

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de seanb4t/codegraph-go

Todos los issues de seanb4t/codegraph-go

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.